Lag

A planned waiting period that delays the start or finish of a successor activity relative to its predecessor in a dependency link.

Key Points

  • Lag is a delay applied to the relationship between activities (FS, SS, FF, SF), not to the activities themselves.
  • It is usually a positive duration that postpones the successor; a negative value would represent a lead (accelerating the successor).
  • It models non-work waiting time such as curing, drying, shipping, or approval wait periods.
  • Defined in the schedule network as a duration or time unit on the dependency link and does not consume resources.

Example

Activity A: Pour concrete. Activity B: Strip forms. The relationship is Finish-to-Start with a 2-day lag to allow the concrete to cure. B cannot start until 2 days after A finishes.

PMP Example Question

A schedule shows Activity B cannot start until three days after Activity A finishes, even though A is complete. What is this three-day period called?

  1. Lead
  2. Float
  3. Lag
  4. Management reserve

Correct Answer: C — a planned delay between a predecessor and its successor

Explanation: Lag is the intentional waiting time inserted on a dependency link; lead accelerates the successor, float is schedule flexibility, and reserves are contingency buffers.

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.

Seven 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


Take Control of Project Performance!

HK School of Management helps you go beyond status reports and gut feelings. In this advanced course, you will learn Earned Value Management (EVM) to measure progress, forecast outcomes, and take corrective action. Learn how WBS quality drives performance, how control accounts work, and how to use EAC, TCPI, and variance analysis. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More