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

Project Portal
| ### Next Steps Define Risk Parameters |
| Determine Risk Sources and Categories ( 3 : RSKM : 1 : 1.1 ) Project Manager
Activity: Determine Risk Sources and Categories
Project Manager
|  |  |  | Planning |  |
|  | Participating Roles Responsible: Project Manager Accountable: Project Manager Consult: Any
### Overview Based on the vision statement and related domain knowledge, brainstorm a list of risk sources and categories. # Entry Criteria Vision Statement The vision statement for the product. Business Case The business case constructed by the product manager for the product. Strategic Planning The strategic planning for the organization including competitive positioning, vectors of differentiation, and market forces analysis. Organization Data Warehouse Reports Reports from previous projects with data on risks, issues, productivity, and special and common cause variation in project execution. # Sub-Activities
1 | List Relevant Risk Categories | Risk categories can include; Dependencies across the organization and technical dependencies on components, architecture, and other parts within a program. Requirements uncertainty due to lack of good product vision, lack of understanding of the market place, poor strategic planning, lack of maturity of the market segment, no established go-to-market strategy, or competitive maneuvers which can affect the original positioning of the product. Management issues such as inadequate planning, poor understanding of variation, lack of transparency, lack of slack time to absorb variation, unclear ownership, poor definition of roles and responsibilities, unrealistic commitments, poor estimation, unreasonable expectations, dysfunctional behavior left uncorrected, poor communication, or poor leadership. Lack of knowledge in the domain or technical aspects of the product, lack of training in tools and techniques required to build the product, lack of training in the process used on the project, use of new technologies not well understood, or ineffective or poorly understood processes. Resource issues such as unavailability of equipment, lack of facilities, lack of personnel or key specialist skills unavailable when required, or lack of backup for critical limited resources. Staff turnover and other personnel issues including outage for birth, death in the family, marriage, illness, disability. Culture and language issues with multi-location teams, or localization issues with products which are translated and localized for multiple countries/regions and cultures. Localization adds significantly to scope, verification, and validation activities. Poor architectural choices or bad technical approaches. This is a secondary effect of a lack of skills and knowledge, but it can lead to significant unplanned rework and missed dates. Create a list of the risk categories which are right for your project and product vision.
2 | Identify Risk Sources | Risk sources will be monitored for signs of risks materializing. Risk triggers will be set against risk sources. Sources may include: Personnel records. Requirements, vision statement, business case and strategic planning materials. Version control and document servers. Plans, estimates, budget, financial records, and analysis work products. Architecture and design documents and models. Make a list appropriate for your project and product based on the categories of risk already identified.
# Exit Criteria
| A document listing the desired categories and the identified sources of risk information.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |