Activity: Manage Baselines & Releases








var defaultQueryStr = '?proc=_MiAAUSJaEdqQipbmJ0SDbw&path=_MiAAUSJaEdqQipbmJ0SDbw,_o6SpgDHaEdqLw-lQEI8RPw';
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=null;
contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, false, true, false);










Activity: Manage Baselines & Releases















This activity ensures that consistent sets of related or dependent artifacts can be identified as part of a "baseline" for various purposes, such as the identification of release candidates, product versions, artifact maturity or completeness.


Extends: Manage Baselines & Releases








DescriptionWork Breakdown StructureTeam AllocationWork Product Usage








Relationships



Parent Activities


Ongoing Management and Support






Description



The frequency and formality in which baselines are created are described in the CM Plan. The degree of formality is clearly much higher for a product being released to a customer than for executable releases within the internal project team. When the combined set of artifacts reach certain stages or levels of maturity, baselines are created to assist managing availability for release, reuse and so forth.



Properties



Event Driven


Multiple Occurrences


Ongoing


Optional


Planned


Repeatable



Staffing



This work is primarily driven by the Configuration Manager role, where the typical need is to be able to assemble a product for release. The released product requires a Bill of Materials (BOM) that serves as a complete checklist of what is to be delivered to the customer. The released product will inevitably require release notes and training material as described in the Deployment activities. The Integrator role contributes to this work by ensuring that artifacts delivered from the developer workspaces are integrated such that they can be incorporated into a independently testable build. The person playing the Integrator role needs to be familiar with Project CM Policies and Test Practices.



Usage



Usage Guidance Typically this work starts in Elaboration, though it is most prevalent in the Construction and Transition phases. In some cases there may be value in baselining Inception artifacts, but this is not the general case. Multiple baselines may be created and managed within a single iteration and may happen at any stage during the iteration. As a general rule, this work is optional if an executable release does not need to be externally delivered outside the core development team.





©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();