LEARN. PRACTICE. GROW.Concept and mechanism
A useful event enables inspection of information and adaptation of work. In the Daily Scrum, Developers assess progress toward the Sprint Goal and adjust their plan; they need not report individually to the Scrum Master. They can choose a structure serving that purpose within fifteen minutes. The Sprint Review involves the team and stakeholders in inspecting results and context to guide adaptations. The Retrospective seeks improvements in quality and effectiveness. A facilitator clarifies purpose, needed information, participation, time, and expected outcome, intervening when format prevents useful discussion. Facilitation does not mean imposing the solution or speaking for most of the session.
Guided application
In a fictional distributed meeting, two people dominate discussion while others remain silent. One complementary technique is 1-2-4-All from Liberating Structures: individual reflection, pairs, groups of four, and collective synthesis. Use it when it helps include perspectives, adapting logistics and accessibility to the group. It is not a mandatory Scrum event and does not replace the meeting purpose. Prepare a concrete question, allow reflection, and confirm understanding before deciding. In professional English, What evidence would change our view? can help explore hypotheses without turning disagreement into a vote about who has more authority.
The format should serve inspection and adaptation with real space for different perspectives.
Common pitfalls
Daily as reporting to a boss; Review as a presentation without dialogue; mandatory technique for every problem.
Related topics: Accountability and service to the team · Goals, planning, and interruptions · Quality, flow, and impediments
Facilitate participation and check whether discussion produced a useful next step.
Reference: 1-2-4-All · Scrum Guide November2020; Kanban Guide May2025; EBM May2024; primary guidance reviewed 2026-09-30