Your team runs every ceremony and still can't say when. Stand-ups happen, sprints close, and a stakeholder asking "when will this be done?" still gets a shrug. The ceremonies aren't the delivery system — and the gap between them is where projects quietly slip. This guide is how to close it.
Haven't taken the check yet? Do that first — 14 questions, about four minutes. It scores you on the three areas below and tells you which one to fix first. Already have your result? Jump to your weakest area: Agile in practice · Delivery flow · Outcome ownership.
Three things decide whether work actually ships. A strong one can't cover for a weak one: great practice with broken flow still can't commit to a date; great flow with no ownership ships the wrong thing well.
The check scores each and gives a combined grade. The engagement, in a sentence: find the weak one and fix it first.
Practice is whether the ceremonies produce anything. The test: does every sprint end with something a user could actually use — not "nearly" — and does the retro change something the team can feel?
Make "usably done every sprint" the non-negotiable, give the PO real authority to prioritise, and use the retro to fix one systemic thing at a time. Certification-style training helps the vocabulary; the habit comes from doing it.
The ceremonies run — now make them mean something. Tighten the definition of done, hold the line on mid-sprint changes (renegotiate, don't absorb), and shift estimates from promises to tracked forecasts.
Protect it: keep the PO's mandate real as stakeholders multiply, keep retros producing change, and don't let "forecast" quietly slide back to "commitment".
Flow is whether work moves predictably from idea to shipped. Predictable, not faster — the goal is being able to give a stakeholder a date and usually be right.
You can't manage what you can't see. Start measuring cycle time, cap work in progress, and make releasing routine rather than an event. Predictability comes from limiting flow, not from working faster.
Flow is improving but still lumpy. Enforce the WIP limit, manage cross-team dependencies before they bite, and get releases boring. Then you can give stakeholders dates you'll actually hit.
Keep the metrics live, keep designing dependencies out of the work, and watch for WIP creeping back up as demand grows.
Ownership is whether "done" means value in users' hands and someone is on the hook for whether it delivered. Dev-complete work that sits is inventory, not value.
Close the gap between "done" and "shipped" — dev-complete work that sits is inventory. Name an owner for the outcome of each significant piece, and start measuring whether shipped work did what it was meant to.
Outcomes are tracked for the big bets — extend it. Give the outcome owner the mandate to change course, measure value routinely, and when delivery slips, look at the system before the people.
Keep value measurement feeding prioritisation, keep "done" meaning in-users'-hands, and keep the blameless response to slippage — it's the first thing to erode under pressure.
Scrum Toolkit runs every ceremony by the 2020 Scrum Guide in a single page — useful when you're tightening practice and want the format straight. Free public beta.
If the weak area won't move — flow stays lumpy however hard people push, "done" keeps not meaning shipped, the PO can't hold the line — that's the point to bring Jon in on that one problem. A short, hands-on look at how work actually flows and where it stalls, then the specific move: training, a process redesign, or a fractional delivery lead on it.