What teams taught me by failing safely

Failure 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 safely

Agile as a learning system, not a delivery framework

Agile is often described as a way to deliver work faster.

That is not wrong, but it is incomplete.

At its best, Agile is not simply a delivery framework. It is a learning system. It helps teams discover what is true, what is valuable, what is possible and what needs to change.

Continue reading Agile as a learning system, not a delivery framework

Scrum Masters and Cynefin – where learning matters most

This is the third post in a short series exploring the Scrum Master role through the four main Cynefin domains:

  • clear
  • complicated
  • complex
  • chaotic

The first post looked at the clear domain, where simple rules and repeatable practice can help.

The second post looked at the complicated domain, where teams need expertise, analysis and informed judgement.

This post looks at the complex domain.

What is the complex domain?

In the complex domain, the relationship between cause and effect can only be understood afterwards.

The work is uncertain. The team cannot simply apply a checklist or ask an expert for the right answer. There may be no single right answer.

Instead, the team needs to learn through action.

Continue reading Scrum Masters and Cynefin – where learning matters most

Psychological safety in Scrum teams and the complex domain

Psychological 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.

Continue reading Psychological safety in Scrum teams and the complex domain

Scrum events as Cynefin domain transitions

One 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