Tag: sprint goal

Agile delivery: what could wait so the important work can finish?

In Tuesday’s post, I explored why agility needs boundaries: clarity about what we protect and what we can change.

Now consider what happens when those boundaries meet a difficult deadline.

There is more work left than the team can realistically finish. What changes next?

Make scope the conversation

DSDM offers a deliberate approach: protect time, cost and the agreed quality standard, then vary the features delivered.

Try bringing that thinking into your next planning conversation.

Continue reading Agile delivery: what could wait so the important work can finish?

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

A moment of deliberate non-intervention

Sometimes the most important thing a Scrum Master does is not visible.

They do not interrupt.
They do not rescue.
They do not explain.
They do not tidy up the conversation too quickly.

They wait.

Not because they are passive.
Not because they are unsure.
But because the team may need the space to work something out for themselves.

Continue reading A moment of deliberate non-intervention

The Daily Scrum is a synchronisation ritual, not a status update

Photo by Ahmet Kurt on Unsplash

Many teams treat the Daily Scrum as a status update.
A quick round of “what I did yesterday… what I’m going to do today… no blockers” before getting on with ‘real’ work.

But that misses its real purpose.

The Daily Scrum is a synchronisation ritual, not a reporting meeting.

At a neurocognitive level, it is about entrainment, the process where one system’s rhythm synchronises with another. Within a team this is about aligning human attention, intent and energy to a shared rhythm.

When done well, it creates temporal coherence. The team develops a common sense of time, direction and progress, much like pendulum clocks gradually syncing when placed on the same wall. Or rowers moving to the vocal rhythm of the cox.

This is why a good Daily Scrum feels different.
It sharpens focus.
It restores momentum.
It reconnects people to the sprint goal.

The most important question is not “What did you do?”
It is “Are we still marching together?”

When teams stay in sync, the work flows.