Skip to content
PMPCAPM

Internal Dependencies

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

Share:

Know it well enough for the exam? Questions on Internal Dependencies are scenario-based, not definitional.

Practice it free

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

High-yield topics our learners drill most before exam day.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Resource Smoothing

Resource smoothing is a resource optimization technique that adjusts activities within their available float so that resource requirements do not exceed predefined limits, without changing the project end date.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Part of

Schedule Management

Study full domain →

Practice Internal Dependencies

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.