Summary

Participate with relevant stakeholders to identify, negotiate, and track critical dependencies.

Description

Example Work Products



  1. Defects, issues, and action items resulting from reviews with relevant stakeholders
  2. Critical dependencies
  3. Commitments to address critical dependencies
  4. Status of critical dependencies


Example Supplier Deliverables



  1. Status of critical dependencies


Subpractices

1. Conduct reviews with relevant stakeholders.

It is particularly important that acquirers or owners of systems that interact with the project in a system of systems be involved in these reviews to manage critical dependencies these types of systems create.



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.

The acquirer documents supplier commitments to meet critical dependencies in the supplier agreement. Supplier dependencies and acquirer dependencies are documented in an integrated plan.



6. Track the critical dependencies and commitments and take corrective action as appropriate.

Refer to the Project Monitoring and Control (PMC) (CMMI-ACQ) 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