How to know your sprint will miss — before it starts

Here's the pattern almost every missed sprint follows. Planning goes well, everyone's optimistic, the board fills up. Around day seven it becomes obvious there's too much. At the review, someone explains why.

The uncomfortable part: it was knowable on day one. You had the committed points and you had your history. Nobody put the two numbers next to each other.

The comparison that matters

Take what you just committed to and divide it by your rolling average over the last few sprints. Above about 110% and you're gambling. Above 130% and you're not planning, you're hoping.

Teams skip this not because it's hard but because it's slightly awkward — it turns an energetic planning meeting into a subtraction exercise. So it gets skipped, and the subtraction happens later, in public.

Making the warning automatic

VectorKan runs that comparison for you and says it in plain words rather than drawing a chart and leaving you to interpret it. During planning you'll see something like:

Overcommitted — this sprint is 140% of your usual velocity. About 14 points are unlikely to land.

That sentence changes the meeting. "Are we sure about this?" is easy to wave away. "About 14 points won't land" starts a conversation about which fourteen.

What to do when you're warned

• Cut whole items, not corners on all of them. Six finished features beat nine at 80%, because 80% of a feature ships to nobody.
• Cut before the sprint starts, not on day eight. Work already begun is far harder to drop — people are invested and context is loaded.
• Tell whoever asked for the dropped item now. A week's notice is a scheduling change; a day's notice is a broken promise.
• Leave the reserve empty. If you always get pulled into support, plan for it rather than pretending each interruption is a surprise.

The knock-on effect

Teams that plan realistically hit their sprints, and teams that hit their sprints get trusted with dates. That's the actual payoff — not the accuracy of the forecast, but the fact that people outside the team stop treating your estimates as opening offers.

VectorKan builds the velocity history automatically as you complete sprints, so the forecast gets sharper the longer you use it. There's nothing to maintain — you just start seeing the warning when it applies.