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

Project Portal
| Manage Change Requests ( 2 : CM : 2 ) ( 2 : GG : 2 : 2.6 ) Business Analyst
|  | Participating Roles Responsible: Business Analyst Release Manager
### Overview Change requests are used to track and control all changes to the product and supporting systems (such as the configuration system). All change requests are initiated as the result of a defect found in a baseline. For example, if a meeting with the user uncovers new requirements, a defect is created documenting that the current requirements baseline is out-of-date. A change request must be created to propose bringing the requirements baseline up-to-date. All change requests are extensively analyzed for impact on the user, product, and teams. All change requests are reviewed by the change control board. The change control board has sole authority for accepting or rejecting change requests. If a change request is accepted, it is scheduled to be implemented for a future iteration. # Entry Criteria Defect. Defect. # Activities
1 | Create Change Request | Analyze Defect Analyze Change Relationships Create Proposed Solution Create Change Request Work Item
2 | Analyze Change Request | Analyze Impact Document Detailed Changes Review Before Submission Record Details of Change
3 | Prioritize Change Requests | Examine requirements list Set Priority Expedite Change Request Reassign Change Request
4 | Review Change Requests | Prepare for Review Meeting Hold Review Meeting Approve Change Request Reject Change Request Defer Change Request Communicate Changes
5 | Track Change Requests | Monitor change request trends and specific issues. Escalate issues, as necessary.
# Exit Criteria
| Accepted or rejected change request.
| Proposed solution document.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |