Here are my notes after working with more than 200 Scrum Teams for 10+ years.

Notes for Scrum Masters and Agile coaches

These reflections draw on my experience working with more than 200 Scrum teams over more than ten years. They are practitioner observations, not a controlled study or a guarantee that the same intervention will work in every organization.

Stay curious and make room for disagreement

Experience does not remove the need to learn. Ask what you may be missing, invite people to challenge your interpretation, and show the openness you expect from the team. Professional credibility depends on observable conduct: listening, keeping commitments, and treating colleagues respectfully.

Look beyond the immediate incident

When a problem repeats, examine the conditions that sustain it. Decision rights, competing goals, dependencies, and feedback delays can explain more than an individual’s behavior. Look for reinforcing and balancing feedback loops before deciding where to intervene.

This does not remove personal accountability. It helps distinguish a behavior that needs addressing from a structure that repeatedly encourages it.

Change deliberately and observe the result

Improvement takes time. If you introduce many interventions at once, it becomes difficult to understand which one helped. Start with an explicit hypothesis, agree what evidence would support it, and review what happened with the team.

Scrum patterns and Lean tools can suggest an approach. They do not replace understanding the circumstances. Explain why a practice might help before asking people to adopt it.

Work with the surrounding organization

A team cannot be isolated from leadership, customers, or other teams. Make dependencies visible and involve the people who can change them. Protecting focus should not mean excluding the stakeholders whose support the team needs.

Use retrospectives to learn

A retrospective technique is useful only if it helps people understand their work and choose an improvement they can pursue. Listen for ideas from everyone, including people who are less comfortable speaking. Avoid treating the method itself as evidence of progress.

Keep the work humane. Curiosity, patience, and enjoyment make sustained improvement easier to practice.

Suha Selçuk. Originally published in 2022; language and structure edited in September 2026.