Guideline: Change Requests |
This guideline describes the type of information that is typically captured on a change request. This information is used to prioritize and scope the work required to implement the change and to monitor progress.
Relationships
Related Elements | Configuration & Change Management Request Change
Main Description
Change requests typically have a lifecycle. They are raised, reviewed, accepted or rejected, implemented, verified and closed. These states define the status of the change request at a particular point in time and represent critical information for tracking progress. Other sets of states are possible. During review of a change request, the goal is to assess the technical, cost, and schedule impact of implementing the change. The technical impact assessment includes the determination of which work products are affected and an estimate of the level of effort required to change and verify all affected artifacts. This information becomes the basis of the cost and schedule impact assessments and, ultimately, whether the change request will be accepted or rejected. If accepted, the implementation and verification of the change request will be assigned to an iteration in the same manner as any other work item. The current process uses the Artifact: Work Items List to capture, prioritize, and track the change requests using the attributed defined for that artifact.
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright