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

Project Portal
| ### Next Steps Create Configuration Management Plan Establish Configuration Management System |
| Review Configuration Management Guidelines ( 2 : CM : 1 : 1.1 ) ( 3 : IPM : 2 : 2.1 ) ( 2 : VER : 2 : 2.2 ) Release Manager
Activity: Review Configuration Management Guidelines
Release Manager
|  |  |  | Planning |  |
|  | Participating Roles Responsible: Release Manager
### Overview Before establishing a configuration management baseline for a new team project, you need to review the configuration management guidelines established by corporate policy for all projects. Not all guidelines apply to every project. You must tailor the guidelines to the needs of the specific team project. Each team project has different needs depending on attributes such as security, quality control, planned releases, method of gathering change requests, auditing standards, and the size of the team and scope of the software product. # Entry Criteria Configuration management guidelines. Configuration management guidelines. # Sub-Activities
1 | Examine Security Needs | Examine the configuration management guidelines concerning security. Look for security guidelines that apply to your team project. A high security project requires tighter control over source code and related configuration management items.
2 | Examine Reporting Needs | Determine which reports different stakeholders need. Examine the guidelines for types of reports required, who needs the reports, and when they need the reports.
3 | Examine Release Needs | Determine how many releases occur before the final release of the product. How will the releases be distributed to end-users or stakeholders? What is the expected quality of each release? Choose branching and integration strategies that support these releases.
4 | Examine Change Request Sources | Determine how change requests originate on the team project. How will end-users evaluating the product submit change requests or bugs? Will they use Internet Web sites, e-mail, or participate in guided usability studies. How will team members and stakeholders submit change requests? Choose guidelines appropriate for the technology used and for how users will evaluate the product.
5 | Examine Auditing Standards | Examine the corporate auditing standards for configuration management. Use guidelines that ensure compliance with these standards.
6 | Examine Size and Scope | Examine the estimated size of the team, and scope of the planned software product. For larger team size or scope, consider branching and integration strategies that enable stable development by different teams that are dependent on using each other's code. For smaller team size or scope, consider simple code management strategies that enable faster code development.
# Exit Criteria
| Tailored configuration management guidelines.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |