The hidden life of agile work: follow one item through its waiting

Earlier this week, we looked at the gaps between active steps: the time when an item is ‘in progress’ but nobody is working on it.

To make those gaps visible, follow one item through its journey.

Start small.

Choose a recently completed piece of work and reconstruct what happened from the moment it started to the moment it finished.

Continue reading The hidden life of agile work: follow one item through its waiting

The hidden life of agile work: most delays happen while nobody is working on the item

An item can spend days ‘in progress’ while nobody is actively working on it.

Someone has started it. Everyone involved is busy. Yet the item is waiting for an answer, a review or its turn in somebody else’s queue.

If we want to understand why delivery takes so long, we need to notice the gaps between the work.

Continue reading The hidden life of agile work: most delays happen while nobody is working on the item

What the age of unfinished work can tell us

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 us

The Sprint ends, but the work’s history does not disappear

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 disappear

How to influence when slowing down is the right move

One of the harder parts of being a Scrum Master is this: sometimes you can see that a team needs to slow down, but managers or stakeholders want the opposite.

That is understandable.

From the outside, slowing down can look like reduced effort.
But in practice, reducing overload is often how delivery improves.

The key is not to argue for ‘slowing down’ in the abstract.

It is to help people see that too much work in progress, too many competing priorities and too much pressure to start work are often the very things that stop work from finishing.

Continue reading How to influence when slowing down is the right move