Skip to content
PMPCAPM

External Dependencies

External dependencies involve a relationship between project activities and non-project activities that are outside the project team's control.

Share:

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

Practice it free

Explanation

External dependencies exist when project activities depend on factors outside the project team's authority or control. These dependencies typically involve third parties, regulatory bodies, vendors, or other projects within the organization. Because they are outside the team's direct control, external dependencies introduce additional uncertainty and risk into the schedule.

Examples of external dependencies include waiting for a government agency to issue a permit before construction can begin, depending on a vendor to deliver equipment before installation activities can start, or needing another project team to complete an interface before integration testing can proceed. These dependencies cannot be managed solely through internal project decisions.

External dependencies require proactive monitoring and communication with the external parties involved. The project manager should track the status of external dependencies closely and may need to build buffer time into the schedule to account for potential delays. External dependencies can be either mandatory (legally required permits) or discretionary (choosing to wait for a vendor recommendation rather than proceeding independently).

Key Points

  • •Involve relationships with activities outside the project team's control
  • •Include vendor deliveries, permits, regulatory approvals, and other project outputs
  • •Introduce additional risk and uncertainty into the schedule
  • •Require proactive monitoring and communication with external parties

Exam Tip

External dependencies are outside your control, so they carry higher schedule risk. Build buffers and monitor them closely.

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 External Dependencies

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