Cadence matters more than many teams realise

When work feels messy, priorities shift, and people are pulled in different directions, Scrum’s regular events can look like admin overhead. But at their best, they do something more important than enforce process. They create coherence.

Scrum events are a shared rhythm

A good Scrum team does not rely on constant supervision. It relies on shared understanding.

That is where cadence helps.

Continue reading Cadence matters more than many teams realise

Better than brainstorming: how Scrum teams should generate ideas

Brainstorming has had a huge influence on modern work.

Many teams still assume that if you put smart people in a room, ask them to suspend judgement and generate lots of ideas, the best solutions will emerge.

But the research on classic spoken brainstorming has long been less flattering than its reputation. People often generate more ideas, and sometimes more original ones, when they think on their own first and then combine their ideas later. One reason is ‘production blocking’ – in a live discussion, only one person can speak at a time, so other thoughts get delayed, diluted or lost.

Continue reading Better than brainstorming: how Scrum teams should generate ideas

When agile teams stop performing progress…

When Agile drifts towards control rather than responsiveness, it is easy to turn Scrum events into performances.

Safe. Polished. Predictable. But quietly useless.

I saw this first-hand when I started as a Scrum Master in a new organisation.

I ran our Sprint Reviews as real conversations, not controlled presentations – and that shift towards openness and responsiveness was genuinely liberating for the team.

Continue reading When agile teams stop performing progress…

What Scrum Masters do when they ‘do nothing’

There are moments in Scrum Mastery where it looks like they’re doing very little.

They’re quiet in a meeting.
They don’t jump in to fix a problem.
They let a conversation run longer than feels comfortable.

From the outside, it can look like inaction.
From the inside, it’s some of the most deliberate work they do.

Continue reading What Scrum Masters do when they ‘do nothing’

Scrum Master as systems steward, not process police

The common misunderstanding

One of the most persistent misunderstandings about the Scrum Master role is that it exists to enforce process.

  • Ceremonies must happen.
  • Rules must be followed.
  • Frameworks must be complied with.

Seen this way, the Scrum Master becomes a kind of process police officer – checking attendance, correcting behaviour and reminding people what Scrum says should happen.

But that framing misses the point of the role entirely.
Scrum does not exist to be obeyed.

It exists to help teams work effectively in complexity.
And complexity does not respond well to enforcement.

Continue reading Scrum Master as systems steward, not process police