Task: Change and Deliver Configuration Items
Manage project artifacts and the work involved from their initial creation as private artifacts through to their delivery and general availability to the project team and other stakeholders.
Disciplines: Configuration and Change Management
Purpose

To ensure that developers follow 'check-in and check-out' procedures to make changes to version controlled work products and delivering changes from a development workspace to the integration workspace.

Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
    • None
    Outputs
      Steps
      Update Workspace

      It is an essential part of any CM system to ensure that work products are under version control, and that team members have access to approved baselines. The idea of updating views to ensure access to the most recent collective body of work is obvious. This should occur on an ongoing basis.

      Each team member having updated a view, can work on any work product through the standard process of 'check-out, edit, build, unit test, and check-in' as described in further steps. 

      Make Changes

      Check-In and Check-Out are the operations that enable development staff to obtain a particular version of a work product, make changes to it, and re-submit it to become the latest controlled version.


       

      Deliver Changes

      Prepare for Delivery Changes:

      Delivery addresses the notion of integration of work from streams of implementers. Delivery is an important step that implies that a developer considers his work to be of sufficiently high quality to be incorporated into the overall product.

      All files are checked-in prior to delivery. This avoids the situation of having orphaned files that are not included in a build and might be needed for subsequent updates.

      The developers build and test their work in their development areas against the work included in the most recent stable baselines before they deliver to the integration workspace. This minimizes the amount of merging that developers must do when they perform deliver operations. 

      Deliver Changes:

      The developer is required to merge his/her changes with those made by other developers. This is typically done in a private integration workspace, so that the merged changes may be tested prior to final delivery to the project integration workspace. The delivery is complete when all merge changes have been checked-in and delivered.