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:

  • clear
  • complicated
  • complex
  • chaotic.

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

This post looks at the complicated domain.

What is the complicated domain?

Hand-drawn Cynefin framework diagram showing four domains around a central area of confusion: complex, complicated, chaotic and clear, with each domain labelled with its constraint type, response pattern and practice type.
A line drawing of the four regions of the Cynefin framework: Clear, Complicated, Complex, and Chaotic, plus the central unknown area Confusion. (Source: Wikipedia)

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.

Continue reading Scrum Masters and Cynefin – when the team needs expertise

Cynefin and Scrum – why Scrum works best in the complex domain

In the previous posts in this series, we explored the Cynefin framework and the role of constraints.

Now we can connect that lens to something many teams use every day: Scrum.

A powerful insight emerges once you see it: Scrum is not really a delivery framework. It is a way of working designed specifically for the complex domain.

Continue reading Cynefin and Scrum – why Scrum works best in the complex domain