All laws

Column7 laws, read in order

Why estimates slip

Estimates tend to slip one way, late, and the reasons are well known. This column reads from the estimate itself, to how work behaves once it starts and while it waits, to what a late project tempts a team to do, and then to planning that expects the slip.

  1. You might hope tasks that come in under would offset the ones that run over. Tasks that could finish early tend to expand to fill their time, so early finishes may not offset the late ones.

    Parkinson's Law

    § 40 · OrganizationWork expands to fill the time available for it.Keep in mind: Give open-ended work a short box
  2. One delay sits outside every task's estimate: by the same arithmetic as for servers, a team whose every hour is booked can expect new work to wait in line before it even starts.

    Kingman's Formula

    § 112 · PerformanceAs a server's utilization approaches 100%, the time work spends waiting for it climbs steeply, and variability in arrivals and service multiplies the climb.Keep in mind: Keep headroom wherever someone is waiting on the answer
  3. Besides adding people, a late project can move the date or the scope. Moving the date is padding by another name, and padding tends to get used up. Moving scope is the one that can be planned in from the start.

    Fixed Time, Variable Scope

    § 89 · EstimationWhen scope is fixed and time is not, the date slips and the scope stays; fixing the time instead forces a choice about what matters.Keep in mind: Decide what the work is worth before you ask how long it takes