SAFe 4.0, Custom tags - mega project management support in Collaborative Lifecycle Management
VidhyaV 270001DB84 Visits (15464)
Two of the new features in Coll
Managing the myriad artifacts and environments associated with each component requires a sophisticated tool. Dependencies between components must be tracked and updated as the product and its components move through different versions and lifecycle stages.
Those of us familiar with CLM 6.0 would know that it creates ‘global configurations’ that link together inter-dependent artifacts across lifecycle stages. For instance, you might want to connect the test cases for a particular sales invoice component with its use case description. If so, you would certainly love the idea of having all the artifacts associated with the invoice – use cases, test scripts, deployment scripts, configuration files, environment settings, and user help - linked together even when all the artifacts are not produced with the same tool or by the same team. This is what CLM 6.0’s glob
The ability to navigate and search components is enhanced in 6.0.2 by the custom tag property. Searching through the hundreds and even thousands of versions of components in a mega project is a daunting task, unless you have some way to tag the components you create. CLM 6.0.2 allows you to create a custom tag in a global configuration, which you can then use as a common mark on similar components.
For instance, if you are developing a large ‘sales-order processing’ system, for hundreds of large customers, you might want the invoicing, contracting, and other services provided by your application to map as closely as possible to client processes. A scalable way to do this would be to represent each customer category by a ‘component’. For example, you could conceive a ‘Defense’ component, that would encapsulate all the invoices, contracts, and processes related to ‘Defense’ customers. To save time and effort during development you would then look for a method to ‘connect’ your code files with the appropriate requirements document and test cases. An easy task if there were only one customer profile, but not a trivial one when there are dozens, each with its own templates, services, test cases, and scripts.
CLM 6.0.2 offers a simple solution by letting you create a ‘global component’ with a ‘custom tag’, say ‘Customer Category’. You can then create a global component called ‘Defense’, for example, which you could use to identify all ‘Defense’ artifacts by populating its Customer Category tag with the value ‘Defense’. By repeating this for other customer categories, you have a consistent and scalable way to organize the various components. If you need to track down ‘Defense’ artifacts you can do so by searching through the global configurations for Customer Category tags that have the value Defense.
SAFe 4.0 (Beta release)
Grouping components together is a problem that is similar to tracking and linking, and just as central to Agile project management. What is the best way to group components?
SAFe 4.0 seeks to address this problem with its concept of ‘value streams’. Value streams are aggregates of components that lie below the portfolio level but above the team and program levels of SAFe 3.0. They are smaller than portfolios but larger than programs.
CLM 6.0.2 supports SAFe
Both custom tags and support for SAFe 4.0 extend CLM’s ability to manage large projects - even the largest. Those of us who appreciate the Agile way of working but have been constrained by tool and team boundaries to apply it to large projects can hopefully see an end to their dilemma with CLM 6.0.2.