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

Project Portal
| ### Next Steps Analyze Change Request |
| Create Change Request ( 2 : CM : 2 : 2.1 ) Business Analyst
Activity: Create Change Request
Business Analyst
|  |  |  | Build |  |  |  | Stabilize |  |  |  | Operational Management |  |
|  | Participating Roles Responsible: Business Analyst
### Overview All change requests originate as a defect against one or more baselines. For example, if a user review identifies new or changed requirements, a defect work item is created to document that the requirements baseline is incomplete. The business analyst reviews all defects that are not code bugs to determine if they are requested changes to baselines, or the product. If a change is needed to fix the defect, the business analyst creates a change request documenting the nature of the change, and assigns it to the project manager for further investigation. This activity should be performed daily by the business analyst. # Entry Criteria Defect requesting change analysis created and assigned to the business analyst. Defect requesting change analysis created and assigned to the business analyst. # Sub-Activities
1 | Analyze Defect | Examine the defect work item. Determine which baselines must change to correct the defect. For example, if the defect describes an existing requirement that must be updated with new information from the user, the requirements baseline will be affected. If the requirement is already designed and coded, the design and code baselines will also be affected.
2 | Analyze Change Relationships | Review historical change requests for relationships to the defect. Determine if similar defects and change requests have been proposed before and what the resolutions were. Use this information to help plan a proposed solution.
3 | Create Proposed Solution | Create a proposed solution for the defect. This will form the core of the change request. For example, if user acceptance testing discovered that users could not figure out how to enter specific data on a form, the proposed solution could require a user interface change to add an additional field into which users can enter that data. Document the baselines affected, and benefits of the proposed solution. If there are alternative solutions to consider, document those as well.
4 | Create Change Request Work Item | Create a change request work item. Document the baselines affected in the Affected Area field. Do not fill in fields for priority, analysis, impact, builds, or changesets. These fields are updated in the Analyze Change Requests activity. Attach the proposed solution to the change request work item if it is a separate document. If the defect affects multiple feature areas of the product or the scope of the change is large, consider creating multiple change requests. Try to create the change requests so that they can be implemented independently from each other. If they are dependent upon each other, be sure to link them together. Link the new change request work item to the original defect work item. This allows anyone investigating or reviewing the change request to be able to examine the original defect behind the change request.
# Exit Criteria
| Change request work item assigned to appropriate project manager.
| Proposed solution.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |