|
|
 |
 |
 |
 |
Activity:
Prioritize Functionality (CMMI Level 3 : RD 3.4 )
 |
|
Participating Roles
Accountable:
Business Analyst |
Once the product requirements are baselined, prioritize the functionality for the project. Indicate the functionality that is mandatory, preferred, or optional. The product requirements can be organized in functional groups or features to facilitate prioritization. The prioritization is used to make decisions about what is to be included in the final product for the project, if business constraints dictate the need to modify the functionality.
Entry Criteria
When:
- After product requirements are baselined.
Dependencies:
- Functional Requirements Baselined: The functional requirements are reviewed, approved, and baselined.
- Interface Requirements Baselined: The interface requirements are reviewed, approved, and baselined.
- Security Requirements Baselined: The security requirements are reviewed, approved, and baselined.
- Safety Requirements Baselined: The safety requirements are reviewed, approved, and baselined.
- Operational Requirements Baselined: The operational requirements are reviewed, approved, and baselined.
Sub-Activities
|
|
1 |
Analyze Customer Needs |
- Analyze the customer needs regarding specified functionality. Understand the value of functionality from their perspective.
|
|
2 |
Analyze Market Forces |
- Analyze the competition and other market forces. Determine which functionality is needed to keep up with the competition, and which functionality will put you ahead.
|
|
3 |
Set Prioritization Level |
- Weigh the customer needs, market forces, and resource limitations against your business goals and schedule. Set the appropriate prioritization level for each functional grouping and/or product requirement.
|
Exit Criteria
 |
The specified functionality to be addressed by the project is prioritized. | |
 |
 |
 |
 |
(C) 2005 Microsoft Corporation. All rights reserved.
MSF for CMMI Process Improvement: Build 050707 |
|
Program Management
