Track change requests for the configuration items.

Change requests address not only new or changed requirements, but also failures and defects in the work products.

Change requests are analyzed to determine the impact that the change will have on the work product, related work products, budget, and schedule.

Typical Work Products

1.    Change requests

Subpractices

1.    Initiate and record change requests in the change request database.

2.    Analyze the impact of changes and fixes proposed in the change requests.

Changes are evaluated through activities that ensure that they are consistent with all technical and project requirements.

Changes are evaluated for their impact beyond immediate project or contract requirements. Changes to an item used in multiple products can resolve an immediate issue while causing a problem in other applications.

3.    Review change requests that will be addressed in the next baseline with the relevant stakeholders and get their agreement.

Conduct the change request review with appropriate participants. Record the disposition of each change request and the rationale for the decision, including success criteria, a brief action plan if appropriate, and needs met or unmet by the change. Perform the actions required in the disposition, and report the results to relevant stakeholders.

4.    Track the status of change requests to closure.

Change requests brought into the system need to be handled in an efficient and timely manner. Once a change request has been processed, it is critical to close the request with the appropriate approved action as soon as it is practical. Actions left open result in larger than necessary status lists, which in turn result in added costs and confusion.