Skip to content
PMPCAPM

Mandatory Dependencies

Mandatory dependencies are those that are legally or contractually required or inherent in the nature of the work, often involving physical limitations.

Share:

Explanation

Mandatory dependencies, also called hard logic or hard dependencies, represent relationships that cannot be changed by the project team. They arise from the physical or contractual nature of the work being performed. For example, in construction, a foundation must be laid before walls can be erected. This is a physical constraint that cannot be altered regardless of project preferences.

Mandatory dependencies are identified during the Sequence Activities process and are distinguished from discretionary dependencies, which the team can choose to modify. Recognizing whether a dependency is mandatory or discretionary is critical for schedule optimization. When the team needs to compress the schedule through fast tracking, only discretionary dependencies can be relaxed. Mandatory dependencies must be respected.

Mandatory dependencies can be internal (within the project) or external (involving outside entities). For example, a contractual requirement to deliver a component by a certain date before the next phase can begin is a mandatory external dependency. Understanding the nature of each dependency helps the project team make informed decisions about schedule changes and risk.

Key Points

  • Also called hard logic or hard dependencies
  • Cannot be changed by the project team
  • Arise from physical limitations, legal requirements, or contractual obligations
  • Must be respected during schedule compression efforts

Exam Tip

When fast tracking, only discretionary dependencies can be adjusted. Mandatory dependencies are fixed and cannot be changed regardless of schedule pressure.

Frequently Asked Questions

Related Topics

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

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

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 is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

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.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Schedule Management

Study full domain →

Test your knowledge

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