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 waitingFailure is not usually something organisations want to talk about.
We prefer words like delivery, progress, efficiency and success. Those are good things. But in Agile work, some of the most important learning comes from small failures that happen early enough to do something about them.
The key is not to avoid failure completely.
The key is to make failure safe enough, small enough and visible enough that the team can learn from it.
Continue reading What teams taught me by failing safelyPsychological safety is often discussed as a team health issue.
It is that.
But in Scrum teams, it is also something more.
It is one of the conditions that makes complex work possible.
Scrum teams are often surrounded by numbers.
Velocity, throughput, cycle time, burndown charts and delivery forecasts can all be useful for a while.
But there comes a point in some conversations when the numbers stop helping.
They are still being discussed. They are still being reported. But they are no longer bringing the team closer to reality.
That is the moment I start listening differently.
Continue reading What I listen for in a Scrum team when numbers stop helpingAgile teams are expected to adapt.
They inspect.
They learn.
They change course.
But adaptation only happens when people feel safe enough to tell the truth.
Continue reading Psychological safety is a prerequisite for adaptation
