Skip to content
PMPCAPM

Internal Dependencies

Internal dependencies involve a relationship between project activities that are within the project team's control.

Explanation

Internal dependencies exist between activities that are both within the scope and control of the project team. Unlike external dependencies, the project team has direct authority over both the predecessor and successor activities. This means internal dependencies are generally more predictable and manageable than external ones.

Examples of internal dependencies include the requirement to complete design before coding begins, or the need to finish unit testing before integration testing starts. In both cases, the project team controls both activities and can manage the relationship directly. Internal dependencies can be either mandatory or discretionary.

An internal mandatory dependency reflects the inherent nature of the work (e.g., you must assemble a machine before testing it). An internal discretionary dependency reflects the team's preferred approach (e.g., choosing to complete all documentation before starting training development, even though some training materials could be created in parallel). Understanding whether a dependency is internal helps the project manager assess how much control the team has over the schedule.

Key Points

  • Both predecessor and successor activities are within the project team's control
  • More predictable and manageable than external dependencies
  • Can be mandatory or discretionary
  • Project team has direct authority to manage these relationships

Exam Tip

Internal dependencies are within your control. Combined with the mandatory/discretionary classification, this creates a 2x2 matrix: internal mandatory, internal discretionary, external mandatory, and external discretionary.

Frequently Asked Questions

Related Topics

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.