Scrum, day 13: helping the team become more effective

Today's objective: choose a Scrum Master intervention that helps the team address a problem while strengthening its ability to manage its own work.

Read alongside: the Scrum Master section of the Scrum Guide and Scrum: A Pocket Guide, fourth edition, §2.5, focusing on the Scrum Master. Allow roughly five minutes for this companion, plus the assigned reading.

A tidy meeting can still leave the problem untouched

Radu, the Scrum Master in our fictional ShiftSwap team, notices a pattern. In the daily conversation, each Developer reports what they did yesterday and then looks at him. He asks follow-up questions, writes down blockers, and sends a summary afterward.

The event starts on time and ends quickly. Yet the same unfinished work appears the following morning. Developers wait for Radu to assign a response to each blocker. Their separate progress reports say little about whether the decline flow will become usable or what they need to change together.

Radu could make the meeting more efficient by collecting updates in advance. That might save a few minutes while preserving the central problem. He first needs to understand what the team is using the event for and which decisions it is avoiding.

The Scrum.org Scrum Master reference ties the accountability to establishing Scrum and improving the team's effectiveness. Scheduling events is one activity that may help. It is insufficient if the events fail to support their intended decisions.

Observe before choosing an intervention

After the conversation, Radu asks the Developers what they need to know to coordinate the day's work. One says she does not know whether the explanation text or the data change is the immediate constraint. Another thought Radu was responsible for deciding the order.

The team has both an information problem and a misunderstanding of accountability. Radu can address them differently. He can explain that the Daily Scrum is for the Developers to inspect progress and adapt their plan. He can also help them examine what their current board fails to show.

A question alone may not resolve a misunderstanding about the framework. A short explanation can be appropriate. Equally, a lecture about self-management would not reveal which particular dependency is stopping the flow. Useful intervention depends on the problem, rather than on always adopting one preferred style.

Facilitate a decision the team can own

With the Developers, Radu proposes trying a different structure at the next Daily Scrum. They begin with the Sprint Goal, examine the work closest to a usable result, and identify the adjustment needed today. The Developers agree to conduct the conversation themselves.

During the first attempt, they discover that a data question is blocking both implementation and verification. Two people agree to investigate it immediately afterward. Another finishes an already-started check. They update the plan together.

Radu's contribution is to help the team understand the event and try a structure that supports its purpose. He does not need to select the two people or dictate their technical approach. If the experiment works, the team should be able to keep using and improving it when he is absent.

Distinguish a team problem from an organizational obstacle

The same conversation reveals a recurring problem outside the team's control. A sponsor sends reporting requests directly to individual Developers and expects them to interrupt their current work. Elena learns about those requests only afterward.

The Developers can make the interruptions visible and discuss their consequences. They cannot resolve the sponsor's expectations solely by rearranging the board. Radu helps bring the sponsor and Elena together to explain the Product Goal, backlog ordering, and the effect of hidden work on the Sprint.

They agree on a way to raise urgent needs with the relevant people and make any resulting trade-off explicit. The agreement needs to work in practice; a process diagram that the sponsor ignores would not remove the impediment.

Helping cause an impediment's removal may mean connecting people, making its cost visible, teaching a missing concept, or challenging an organizational habit. The Scrum Master does not personally control every system or decision involved.

Help the Product Owner as well as the Developers

Elena also needs support. She has been responding to every incoming request immediately, leaving little time to investigate user problems or clarify the next improvements. Radu helps her examine which decisions need her attention and which information-gathering work can be shared.

They consider a clearer way for stakeholders to understand the current product direction and the reasons behind the order. They also review whether Elena has the authority her accountability requires. If every decision needs a committee's permission, better personal organization will not solve the underlying issue.

This is part of serving the whole Scrum Team. Concentrating only on the Developers' meeting habits would miss a product-management constraint affecting everyone's work.

Inspect whether the intervention helped

After several working days, Radu and the team look for evidence. Are the Developers making useful daily adjustments? Does blocked work become visible sooner? Are stakeholder requests discussed with their trade-offs? Can the team explain its current plan without relying on Radu's private notes?

Attendance and punctuality provide some information about events, but they do not establish effectiveness. Nor does a lower meeting count automatically show that the team is collaborating better. The team needs to inspect the decisions, product results, and working relationships that the changes were meant to improve.

Suppose the new Daily Scrum structure produces long technical debates. The team can preserve the useful coordination while moving detailed problem-solving into a follow-up involving the relevant people. It is allowed to improve the technique it chose.

Choose an intervention and an exit condition

Think of a recurring problem in a team you know. Describe the observed behavior, its consequence, and who has the ability to change the relevant conditions. Avoid starting with a prescribed workshop or meeting format.

Choose one intervention: an explanation, a facilitated conversation, a coaching question, practical help, or work with someone outside the team. Explain why it fits this problem. Then state what you would observe if it helped and what the team should eventually be able to do without your involvement.

Reflection: does your proposed help make the team more capable, or make you the necessary intermediary for another decision? If the latter is temporarily unavoidable, describe how that dependency could be reduced.

The next companion examines the Sprint boundary: which commitments remain stable and which parts of the plan can change as the team learns.