A Sprint gives a team a useful rhythm. At its end, we inspect what we have achieved and plan what comes next.
But unfinished work does not become new work just because a new Sprint has begun. It carries its history with it.
Continue reading The Sprint ends, but the work’s history does not disappearA two-week Sprint creates the impression that a Scrum Team learns every two weeks.
But that is true only if useful feedback reaches the team within that period.
A Sprint may end while the work is still awaiting integration, testing, deployment or use by real customers. The Scrum events continue, but the most important feedback arrives several Sprints later.
Continue reading What happens when the Sprint is shorter than the development feedback loop?In the previous posts in this series, we explored the Cynefin framework and the role of constraints.
Now we can connect that lens to something many teams use every day: Scrum.
A powerful insight emerges once you see it: Scrum is not really a delivery framework. It is a way of working designed specifically for the complex domain.
Continue reading Cynefin and Scrum – why Scrum works best in the complex domainWhen Agile drifts towards control rather than responsiveness, it is easy to turn Scrum events into performances.
Safe. Polished. Predictable. But quietly useless.
I saw this first-hand when I started as a Scrum Master in a new organisation.
I ran our Sprint Reviews as real conversations, not controlled presentations – and that shift towards openness and responsiveness was genuinely liberating for the team.
Continue reading When agile teams stop performing progress…
Many people still treat a sprint as a mini project.
Or worse, as a chance to cram in as many tasks as possible.
I’ve seen this everywhere I’ve worked: the sprint backlog becomes a shopping list rather than a coherent plan.
But that isn’t what a sprint is for.
A sprint is a controlled experiment in bounded uncertainty.
It creates a safe container where a team can explore ideas, test assumptions and learn quickly without risking the whole system.
The timebox is the magic.
Limit time and you sharpen focus, shorten feedback loops and accelerate learning.
Remove the boundary and work starts to drift. Energy scatters. Insight takes longer to surface.
Scrum isn’t just about delivering increments.
It’s about running small, structured experiments that help us understand reality faster.
A sprint is not a box to fill – it’s a boundary that helps us think.
