The release plan had two weeks of buffer. Everyone watched it go in, and everyone agreed it was prudent. At PI Planning the team voted confident — not reckless confident, the earned kind: they knew the scope, they knew their throughput, and they knew the margin was real.

Six weeks later the buffer is gone. And here’s the unsettling part: nothing happened. No incident, no re-org, no vendor surprise. The margin simply left the building, and nobody can point to the week it left. Project management has had names for this disappearing act for decades: student syndrome and Parkinson’s Law.

Student syndrome: the buffer spent before work begins

Student syndrome is the name Eliyahu Goldratt gave, in Critical Chain, to a habit everyone recognizes: when a task has safety built in, we start it as late as that safety allows. It’s the all-nighter before the exam, scaled up to a Fix Version. The buffer gets spent at the front of the task, before the first commit lands — exactly where no burndown chart is looking.

On a release plan the behavior is almost invisible. The committed date sits eight weeks out, so the risky migration can wait a sprint. It waits two. Nobody decided to spend the margin; it was simply available, so it went first.

Parkinson’s Law: the buffer absorbed at the finish

Parkinson’s Law is older — Cyril Northcote Parkinson, writing in The Economist in 1955: work expands to fill the time available for its completion. Give a five-day task eight days and it quietly becomes an eight-day task. A little more polish, one more refactor, a finish that drifts toward the deadline and never crosses it early. Neither law is about bad engineers; both are about what any of us does when a deadline still feels far away.

Together the two laws make a quiet pact: tasks that start late and still finish exactly on time. Nothing is ever “late” in a status report until the very end — which is why the buffer’s disappearance never shows up in one. If you’ve ever watched a release burn its entire margin without a single red flag in the tracker, this is the mechanism. The dates on the plan never moved. The room around them got smaller every week.

The confidence vote wasn’t wrong

Here’s what the two laws do not mean: they don’t mean your team’s confidence vote was naive. That vote was expert engineering judgment — the people closest to the work pricing in scope, capacity, and risk, and committing with real margin. It was right on the day it was given.

The problem is what happens after. A static buffer is a snapshot defense: it protects the committed date exactly once, at the moment it’s added. From then on, the margin sits under continuous, silent pressure — and a padded schedule has no instrument on it. You can’t watch a buffer being consumed. You can only discover, late, that it was.

Watching the margin without the ceremony

Goldratt saw this clearly, which is why Critical Chain doesn’t stop at buffers. It adds buffer management: fever charts, burn ratios, weekly reviews of margin consumed against chain completed. The instinct is exactly right — watch the margin, not the tasks. The cost is a parallel bookkeeping system that most Jira teams never sustain past the second sprint.

Release Management, Roadmaps & Product Portfolio for Jira takes the same instinct and puts it on an instrument nobody has to maintain. Your committed date carries a live confidence band — 50/85/95% — re-forecast continuously by Monte Carlo simulation on the team’s actual Jira throughput. The team still owns every assumption behind it: which throughput window reflects reality, whose capacity is in the plan, what’s in scope. The app’s job is the arithmetic, at a scale no ceremony can match, kept current every day.

That changes what student syndrome and Parkinson’s Law can hide. If work is starting late, throughput sags now — and the confidence on the committed date decays now, in days, not in the final sprint. In effect, the band is the buffer: the distance between the 50% date and the level you committed at, recalculated as evidence arrives. When the margin is healthy, everyone can see it. When it’s being eaten, everyone can see that too — while the conversation is still cheap.

Renegotiate before the slip

Buffer-eating habits are one face of a bigger pattern — the three things that erode a committed release date: scope creep, dependencies surfaced too late, and capacity changes. Margin hidden inside individual numbers fails the same way — that’s padding estimates, the schedule buffer’s invisible cousin — and so does the interrupt load the plan never saw. The cure is identical in every case: track the erosion against the committed date while renegotiation is still cheap. “Confidence has slipped from 85% to 70% — do we trim scope or move the date?” is planning when it happens in week three. The same sentence in the final week is an apology.

Your team’s judgment deserves a margin it can actually see. Put a live confidence band on your next Fix Version and watch the committed date the way Goldratt wanted you to watch the buffer — continuously, honestly, and early enough to act.

Rob Borges

Rob Borges spent the first half of his career hunting waste as a Lean Six Sigma Master Black Belt and wrangling portfolios as a PMI Portfolio Manager — until he realized the tidiest process on earth still can't out-plan an optimistic human. So he switched sides and became an Agile Coach. These days he helps Kanban, Scrum, and Agile-at-Scale teams trade gut-feel deadlines for flow data, turning "we'll probably ship sometime in Q3" into release dates leaders can actually take to the board. His rule of thumb: hope is not a forecast, but your throughput history usually is.

See Full Bio