Every fist of five ends the same way. Fingers go up around the room, someone calls out the average, it lands on a four, and PI Planning wraps with real relief. The vote is genuine — the team looked at an actual plan and gave an honest read on the risk. Nobody in that room was guessing.
The trouble starts after the room empties. That four was accurate for the plan as it stood at the moment everyone voted. It says nothing about the plan three sprints later, once a couple of dependencies have shifted, a “quick” scope add landed in week two, and someone’s been pulled onto a production incident for half a sprint. The vote didn’t become less honest — it just stopped being asked. A fist of five is a snapshot of confidence, cast once, at the one moment everyone happened to be in the same room.
For a Scrum Master watching one team, that’s a manageable blind spot. For an RTE watching six teams vote at the same PI Planning, it compounds: six fists of five, six snapshots frozen at the same moment, and no single view of which ones have already drifted furthest from the plan three sprints in.
The vote nobody re-takes
SAFe’s confidence vote was never meant to be the last word on a PI — a low score is supposed to trigger replanning before the PI even starts. What it doesn’t include is a built-in moment to ask again once the PI is underway. There’s no ceremony for interrupting sprint three to hold up fingers a second time, so the number from planning day quietly keeps standing in for “we’re fine” — right up until someone notices, weeks later, that it clearly isn’t, with no clear point where it stopped being true.
That gap is the same one behind the three things that erode a committed release date: scope, dependencies, and capacity don’t move on the PI calendar, so a vote that only happens on the PI calendar can’t track them. Scope alone erodes a plan a few points at a time; add a dependency that surfaces late or a team member pulled onto something else entirely, and the gap between “what we voted on” and “what’s actually true” only widens.
Running the same vote every day
Advanced Release Planning isn’t trying to out-vote the room. It asks the room’s exact question — how confident are we in hitting this date? — of the data instead, every day rather than once. The committed date carries a live confidence percentage — P50, P85, P95 — computed by Monte Carlo simulation against the team’s real throughput, not against how everyone felt at the moment of the vote.
On the Fix Version, it reads the way a fist of five would if you could freeze-frame it: “Aug 14 · 85%,” green at or above the team’s committable line, amber once it slips below, red past the coin-flip mark. Add scope, and the burn-up line steps up and the number moves before anyone thinks to call a meeting about it. Resolve a dependency, or lose someone to unplanned time away, and it moves again — because the inputs changed, not because someone remembered to recast a vote. See how the confidence band relates to the fist-of-five vote in the feature documentation.
For the RTE with six teams, the same view rolls up: instead of six separate memories of what each team voted at planning, one screen shows which committed dates are still green, which have slipped to amber and are worth a real conversation, and which are already red.
Same judgment, kept current
This isn’t a colder, more mechanical stand-in for the room’s judgment — it’s the same kind of judgment, running continuously instead of once. The team still decides what counts as committable; P85 is the common default, the same bar SAFe uses for a committed objective rather than a stretch one. Advanced Release Planning’s job is narrower and more mundane: keep that number honest between votes, so “can we still hit the date?” has a real answer on day twelve, not just a memory of the answer from day one. Nothing about this replaces PI Planning or the vote itself — it just means the room’s judgment doesn’t have to last unchanged for twelve weeks on its own.
A fist of five told your room the truth on planning day. See whether it’s still telling the truth today — try Advanced Release Planning free on the Atlassian Marketplace, or read more on the release planning product page.
2 Comments
Leave your reply.