Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| Change Request
### Work Item Database
Overview |
States and Transitions |
Fields |
### Process Guidance |
Activities |
Workstreams |
Change Request States and Transitions This diagram shows the state transitions for a change request work item. A change request work item identifies a proposed change to some part of the product or baseline. Change requests must be created when a change is proposed to any work product that is in the configuration management system. The change request work item is used by the change control board to analyze, accept, and reject proposed changes. If a change request is accepted, it is used to generate tasks to implement the change. After changes are implemented, the change request is eventually closed. # New A new change request work item is created when a bug identifies a change needed in a work product under change control. ###### New to Proposed
New | A change request is proposed as a new change request when it is first created.
# Proposed Proposed change requests represent changes to the product or a baseline. Proposed changes must be reviewed by the change control board and either accepted or rejected. ###### Proposed to Active
Accepted | A change request is activated as Accepted if the change control board decides that the change is worth implementing.
Investigate | A change request is activated as Investigate if triage determines that an investigation of the impact is necessary before approval is given. Change requests marked Active for investigation should be returned to the Proposed state when the investigation is complete.
###### Proposed to Closed
Rejected | A change request is closed as Rejected if the change control board decides the change is not worth implementing.
# Active An active change request indicates that a change is approved and currently being implemented. ###### Active to Resolved
Code Complete & System Tested | A change request is resolved as Code Complete & System Tested when the code for the change request is written, reviewed, tested, and integrated into the daily build.
###### Active to Closed
Abandoned | A change request is closed as Abandoned if the change request cannot be implemented for some reason. For example, a change request may be abandoned because the original impact estimates were too low and the changes became too costly.
Out of Scope | A change request is closed as Out of Scope if it is no longer an applicable change. This could happen as a result of reviewing the backlog and finding old change requests that have not been completed.
###### Active to Proposed
Investigation Complete | If a change request has been activated for investigation, it should be returned to the Proposed state for re-triage once the investigation is complete.
# Resolved A resolved change request is implemented and system tested and ready for a validation test to ensure the changes are acceptable to the user or customer. ###### Resolved to Active
Validation Test Failed | A change request is reactivated as Validation Test Failed if the validation test fails for any change that was introduced by the change request.
###### Resolved to Closed
Validation Test Passed | A change request is closed as Validation Test Passed when the validation test is passed for all changes introduced by the change request.
# Closed A closed change request means that no further work is to be done for that change request. ###### Closed to Active
Closed in Error | A change request is reactivated if a mistake was made and it should not have been closed yet.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |