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

Project Portal
| ### Next Steps Plan Project Resources |
| Estimate Project ( 2 : PP : 1 : 1.1 ) ( 2 : PP : 1 : 1.2 ) Project Manager
Activity: Estimate Project
User Experience Architect
Business Analyst
|  |  |  | Planning |  |
|  | Participating Roles Responsible: User Experience Architect Business Analyst Accountable: Project Manager Consult: Any Informed: All
### Overview To estimate the project, it is necessary to develop a rough guide to the scope of the project at this early stage. Detailed requirements have not yet been solicited. Detailed planning will be deferred to the start of each iteration. At this stage, conduct a focus group and brainstorming session to identify a minimum set of critical to quality (CTQ) end-to-end scenarios. This minimum set should include all the personas and cover the intent of the product vision. Develop a storyboard for each end-to-end scenario. Gain consensus that this set of scenarios represents the critical to quality success factor for the project. Publish the end-to-end scenarios as the high-level scope of the project. # Entry Criteria Vision Statement The vision for the product. Business Case The case justifying the project. Quality of Service Requirements A list of non-functional requirements or constraints on the functionality of the system is available. # Sub-Activities
1 | Identify End-to-End Scenarios | Hold a focus group and identify a list of end-to-end product scenarios which deliver the essence of the product vision and enable the business case when brought to market. The purpose of this exercise is to identify a minimum set of scenarios which cover the wide scope of the product and deliver the intent of the product vision without getting exhaustive. End-to-end scenarios are long and detailed and involve several personas.
2 | Storyboard End-to-End Scenarios | Develop a storyboard for each end-to-end scenario. Each storyboard should be approximately 40 to 70 panels. There are just a few end-to-end scenarios but they provide a lot of detail and insight into the usage of the product.
3 | Review Storyboards | Review the storyboards with the project team. Has each persona been included? Is there enough content to be compelling for each persona? Has the essence of the vision statement been covered?
4 | Gain Consensus on Critical To Quality Factors | Agree to a consensus on the set of end-to-end scenarios and storyboards as representing the critical to quality (CTQ) and project success factors.
5 | Publish Storyboards | Publish the storyboards so that the whole team might learn and understand the critical to quality project success factors.
# Exit Criteria
| The critical to quality (CTQ) scenarios defining the high-level scope of the project.
| The storyboards of the critical to quality (CTQ) scenarios.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |