Mandatory Dependencies

Required sequencing of activities driven by the work itself (physical or technical limits) or imposed by binding obligations such as contracts, permits, codes, or laws.

Key Points

  • These are non-negotiable, hard-logic relationships that dictate task order.
  • They arise from intrinsic work constraints (physical/technical) or legal/contractual requirements.
  • They cannot be changed without altering scope, method, or constraints.
  • Identifying them early helps build realistic network diagrams and manage critical path risk.

Example

On a construction project, the foundation must be poured and cured before framing can begin (physical constraint). In addition, an approved building permit is required before any structural work starts (legal requirement). Both are mandatory dependencies.

PMP Example Question

Which scenario best represents a mandatory dependency?

  1. The team decides to finish the user interface before the backend to simplify demos.
  2. Concrete must cure before load-bearing walls are erected.
  3. Installation can start only after the vendor ships the hardware.
  4. Work is postponed because the database administrator is on vacation.

Correct Answer: B — A required sequence due to the nature of the work.

Explanation: Concrete curing is a physical constraint that forces the order of tasks, making it a mandatory dependency.

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