Six Sprint Goals, each a variation of “complete the highest-priority stories.” The team runs the events consistently. Sprint Planning is disciplined, the Retrospective is engaged, and the team is capable. And every cycle, the same three impediments surface. No one above the team has defined an outcome, approval decisions land mid-Sprint from outside Sprint Planning, and no one has named the goal. The Scrum Master recognises this pattern and has the accountability to coach executives to close it. The person with that authority doesn’t yet see the gap.
In Brief
- Sprint Goals become completion lists when no one above the team holds the outcome.
- When the Retrospective surfaces the same categories of impediment six times, the Scrum Master can locate the cause above the team.
- The Scrum Guide gives the Scrum Master the accountability to coach executives and stakeholders to optimise their interactions with the team.
- One executive decision, assigning outcome accountability to a single person with Sprint Review authority, changes the Sprint Goal pattern.
Sprint events surface the structural condition above the team
The Sprint Retrospective is the most precise diagnostic instrument available to a Scrum Master, but it only operates on what sits inside the team’s authority.
When six consecutive Retrospectives surface the same categories of impediment (unclear outcome direction, mid-Sprint approvals, no one accountable for the Backlog), the Retrospective is not failing. It is surfacing a structural condition the team cannot resolve. Within the team’s accountability boundary, the improvement cycle builds self-management and raises practice quality: the purpose the Scrum Guide assigns to it (Schwaber & Sutherland, 2020). The Retrospective cannot assign outcome authority to someone above the team. An executive sets that authority above the team, and may not yet recognise that how they have structured it is producing the pattern visible in the event record.
Sprint Reviews show the same gap from the other direction: a team demonstrating working product to people who cannot decide what the organisation does with it. When a Sprint Review generates discussion but no decisions, and priorities shift before the next Sprint Planning, the person with outcome authority is not present. They have not been given the authority to act on what the event record reveals.
The Scrum Guide names the Scrum Master's mandate to coach upward
The Scrum Guide assigns the Scrum Master a specific accountability: coaching executives, sponsors, and business stakeholders to optimise their interactions with the Scrum Team (Schwaber & Sutherland, 2020). That is the structural licence to bring Sprint data to the authority above the team, in terms they can act on.
Hodgson (2026) describes it precisely: no single individual holds accountability for the product outcome, with authority to direct the Product Backlog and act on Sprint Review output. That leaves the team structured for scope delivery, not value creation. The team design may be correct; the authority structure above it is not.
The director or Product Manager can verify the cost: Sprints of capable execution toward scope that may or may not produce the outcome the investment was funded to deliver. The Scrum Master’s accountability is to surface that cost from the event record and bring it to the person who can act on it.
That question, who holds the outcome this team is building toward and whether that person has been given the authority to direct it, belongs at the governance level.
One decision changes the Sprint Goal
The structural change is one governance decision: assign a single individual accountability for the product outcome. That person needs the authority to attend the Sprint Review and direct what gets released between Sprints (Hodgson, 2026).
When that assignment is in place, the Product Owner arrives with an outcome to build toward. The Sprint Goal can name what the team is committed to achieving. The team uses the Retrospective to address what it can actually improve, without cycling through structural impediments it cannot resolve.
One executive decision, assigning outcome accountability with matching release authority, consistently produces this shift; it sits above the team’s authority.
The Scrum Master’s accountability in that transition is to surface the evidence in terms the executive can act on. The evidence is in the event record:
- The Sprint Goal pattern across six Sprints
- The impediment categories the team surfaced in the Retrospective
- The Sprint Reviews where decisions didn’t happen
Naming the Sprint Goal pattern and impediment categories gives the executive what they need to make the structural decision. That naming, specific and evidence-based, is the core of the Scrum Master’s coaching accountability.
When six consecutive Retrospectives surface the same structural impediments (unclear outcome direction, mid-Sprint approvals, no single person with authority to direct the Backlog), that structural condition needs naming. The Zen Ex Machina Governance Diagnostic maps that condition to the specific structural changes that close it.
References
- Hodgson, M. (2026). Evolve: The operating model AI demands. Zen Ex Machina.
- Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. https://scrumguides.org/scrum-guide.html
