evidence

Scrum Masters and Cynefin – when the team needs expertise

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

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

This post looks at the complicated domain.

In the complicated domain, the work is not obvious, but it is still knowable.

There may be more than one right answer. The team may need analysis, diagnosis or specialist input before deciding what to do.

This is the world of expertise.

Scrum and Agile teams are often encouraged to measure their work.

Velocity, throughput, cycle time, burndown charts and delivery forecasts can all offer useful signals.

They can show patterns, reveal bottlenecks and help teams ask better questions.

But most Agile work happens in complex environments, where outcomes emerge, context shifts and people respond to the system around them.

In that kind of setting, metrics do not simply describe reality. They also shape behaviour.

That is where trouble starts.