Participate with relevant stakeholders to identify, negotiate, and track critical dependencies.
Example Work Products
- Defects, issues, and action items resulting from reviews with relevant stakeholders
- Critical dependencies
- Commitments to address critical dependencies
- Status of critical dependencies
1. Conduct reviews with relevant stakeholders.
2. Identify each critical dependency.
3. Establish need dates and plan dates for each critical dependency based on the project schedule.
4. Review and get agreement on commitments to address each critical dependency with those who are responsible for providing or receiving the work product.
5. Document critical dependencies and commitments.
Documentation of commitments typically includes the following:
- Describing the commitment
- Identifying who made the commitment
- Identifying who is responsible for satisfying the commitment
- Specifying when the commitment will be satisfied
- Specifying the criteria for determining if the commitment has been satisfied
6. Track the critical dependencies and commitments and take corrective action as appropriate.
Refer to the Project Monitoring and Control (PMC) (CMMI-DEV) process area for more information about monitoring commitments.
Tracking critical dependencies typically includes the following:
- Evaluating the effects of late and early completion for impacts on future activities and milestones
- Resolving actual and potential problems with responsible parties whenever possible
- Escalating to the appropriate party the actual and potential problems not resolvable by the responsible individual or group