Mandatory Dependency

A dependency where the sequence of activities is dictated by a contract or by the inherent, built-in logic of the work, leaving no practical alternative order.

Key Points

  • Non-negotiable: the order is fixed by contract terms or the nature of the tasks.
  • Often modeled as finish-to-start, though any logical relationship can apply.
  • Misclassifying it as discretionary can create unrealistic schedules and rework.
  • Confirm through contract documents, technical constraints, and compliance needs.

Example

The contract requires customer approval of requirements before design begins, and the structure must be built only after the foundation is poured and cured. Both sequences are mandatory because they are either contractually required or inherent in the work.

PMP Example Question

Which scenario best represents a mandatory dependency?

  1. The contract requires client sign-off on requirements before design can start.
  2. The team prefers to finish user documentation before development for clarity.
  3. Testing is delayed while waiting for a third-party tool license renewal.
  4. Two activities are sequenced because the same engineer is needed for both.

Correct Answer: A — Mandatory dependency

Explanation: Option A is mandated by contract, fitting a mandatory dependency. B is discretionary, C is an external dependency, and D is a resource-driven constraint.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your Agile career!

HK School of Management and Technology helps you learn Agile and Scrum with practical playbooks, AI-powered prompts, and real-world workflows for planning and delivery. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More