LEARN. PRACTICE. GROW.Concept and mechanism
The SM/TC supports team effectiveness through facilitation, guidance, and collaboration on impediments. This does not require personally implementing every fix or automatically grant authority over systems. If a network dependency affects three teams, help make impact and options visible to other facilitators, the RTE, and the technical owner. In a discussion dominated by two specialists, start by making room for evidence and concerns not yet heard. You might invite brief individual reflection, gather options, and compare constraints before deciding. These techniques are contextual choices. Voting cannot waive a mandatory operational requirement or replace the authority responsible for approving change.
Guided application
In a hybrid role, distinguish when you are proposing a technical solution from when you are facilitating the choice. Explain this change of stance and seek another facilitator when needed. To develop self-management, help the team experiment with work-selection criteria instead of assigning every task indefinitely. Follow the experiment’s outcome. Close meetings with agreed actions and follow-up conditions; do not silently assign an obligation to an absent person. When personal attacks occur, address the behavior and return to the observable problem. An incident list may reveal improvement needs without justifying conclusions about individual commitment or competence.
Two teams dispute a load-testing window. Compare needed outcomes and alternatives before splitting time that may be insufficient for either test.
Common pitfalls
Facilitator as universal technical decision maker; autonomy as abandonment; consensus as authorization; throughput without quality.
Related topics: PI Planning, capacity, and dependencies · Iteration execution, flow, and DevOps
The intervention should improve the team’s ability to decide and act responsibly.
Reference: Scrum Master/Team Coach · AI-Empowered SSM; official exam guide August 11 2026