On Tuesday, we looked at a simple idea: a new Sprint does not erase the history of work already in progress.
So what can that history tell us?
Velocity shows how much estimated work a team completed in previous Sprints. Throughput counts the items completed over a period. Both tell us about finished work, but neither tells us how long a particular unfinished item has been in progress or has been waiting.
Continue reading What the age of unfinished work can tell usWhen work feels messy, priorities shift, and people are pulled in different directions, Scrum’s regular events can look like admin overhead. But at their best, they do something more important than enforce process. They create coherence.
A good Scrum team does not rely on constant supervision. It relies on shared understanding.
That is where cadence helps.
Continue reading Cadence matters more than many teams realiseOne helpful way to look at Scrum is to see its events not just as meetings, but as transitions between domains of work.
That is where Cynefin becomes practical.
A team does not stay in one domain all the time. It moves between uncertainty, analysis, action and reflection. Scrum creates a rhythm for doing that well.
Continue reading Scrum events as Cynefin domain transitions
Many teams treat the Daily Scrum as a status update.
A quick round of “what I did yesterday… what I’m going to do today… no blockers” before getting on with ‘real’ work.
But that misses its real purpose.
The Daily Scrum is a synchronisation ritual, not a reporting meeting.
At a neurocognitive level, it is about entrainment, the process where one system’s rhythm synchronises with another. Within a team this is about aligning human attention, intent and energy to a shared rhythm.
When done well, it creates temporal coherence. The team develops a common sense of time, direction and progress, much like pendulum clocks gradually syncing when placed on the same wall. Or rowers moving to the vocal rhythm of the cox.
This is why a good Daily Scrum feels different.
It sharpens focus.
It restores momentum.
It reconnects people to the sprint goal.
The most important question is not “What did you do?”
It is “Are we still marching together?”
When teams stay in sync, the work flows.
