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.
Look beyond the Sprint boundary
A backlog item might appear in this Sprint for the first time, even though the team started it weeks ago. It may have spent time waiting for a decision, moving between people or sitting almost finished.
If we look only at what was completed in each Sprint, that history is easy to miss.
Kanban offers another way to pay attention: follow work from the moment it starts until it is finished. Ask:
- How long has this item been in progress?
- Where has it spent most of that time?
- What is preventing it from moving now?
Keep the story of the work visible
This does not mean abandoning Sprints. It means recognising that a Sprint boundary is a point in time, not a fresh start for every piece of work.
When unfinished work moves into the next Sprint, its age can help the team ask better questions, perhaps:
- the work is larger than expected
- it is waiting outside the team
- too much has been started at once
The calendar has turned. The work has not forgotten where it has been.
Image: Getty Images for Unsplash+
