Each of six Sprint Goals in a row is a variation of “complete the highest-priority stories.” That pattern points to a gap above the team. The team runs every event well: Sprint Planning is disciplined, and the Retrospective is engaged. Yet every Retrospective raises the same three impediments. No one above the team has defined an outcome, approval decisions land mid-Sprint from outside Sprint Planning, and no one is accountable for the Product Backlog. The Scrum Master can see this pattern in the Sprint record and is well placed to bring it to the executives who can change it. Until someone does, those executives see only the stories the team completed.
In Brief
- Sprint Goals shrink to completion lists when no one above the team is accountable for the outcome.
- Six Retrospectives that raise the same impediments show a Scrum Master the cause sits above the team.
- The Scrum Master's accountability to coach the organisation and remove barriers between stakeholders and Scrum Teams includes coaching executives.
- A single, accountable owner for the product outcome, with Sprint Review and release authority, lets the Sprint Goal name an outcome.
Sprint events show what the team cannot change
A Retrospective can change how the team works, but it cannot give anyone above the team accountability for the outcome.
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 doing its job: it is showing a condition the team has no authority to resolve. The purpose the Scrum Guide gives the Sprint Retrospective is to plan ways to increase quality and effectiveness (Schwaber & Sutherland, 2020), and inside the team it does exactly that. The Retrospective cannot assign outcome authority to someone above the team. Only an executive can make that assignment, and the pattern the current arrangement produces shows up in the Sprint record long before it reaches them.
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, no one in the room has been given the authority to act on what the team has shown.
The case for coaching upward starts with the Scrum Guide
The Scrum Guide says the Scrum Master serves the organisation by coaching it in its Scrum adoption and by removing barriers between stakeholders and Scrum Teams (Schwaber & Sutherland, 2020). The Guide does not name executives. Executives sit inside that organisation, though, and in this pattern the barrier is a decision only they can make: who holds the outcome. Coaching them is part of the Scrum Master’s accountability, and it starts with the Sprint data.
In his book Evolve: the Operating Model AI Demands, Hodgson (2026) describes the condition behind this pattern: 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 organised to complete scope rather than to create value. Redesigning the team will not change the Sprint Goal while the authority above it stays the same.
The director or Product Manager can check the cost: Sprints of capable work toward scope that may or may not produce the outcome the investment was funded to deliver. Each Sprint adds to the spend without anyone confirming that the outcome has moved.
Who holds the outcome this team is building toward, and whether that person has the authority to direct it, is an executive decision.
One decision changes the Sprint Goal
The structural change is one governance decision: assign a single, accountable owner 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 will change for the people the product serves. The team uses the Retrospective to address what it can actually improve, without cycling through structural impediments it cannot resolve.
The team cannot make that decision, so the Scrum Master’s part is to bring the executive the evidence for it.
That evidence is already in the Sprint 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
Those records show the executive that the team is completing scope while no one above it is accountable for the outcome the scope was funded to produce. Saying that plainly, with the team’s own records behind it, is the core of the Scrum Master’s coaching.
If your last six Retrospectives surfaced the same impediments (unclear outcome direction, mid-Sprint approvals, no single, accountable person with authority to direct the Backlog), the cause sits above your team, with the executive who can assign outcome accountability. The Zen Ex Machina Governance Diagnostic maps that gap in outcome accountability to the specific structural changes that close it, so you can take one concrete change to that executive.
References
- Hodgson, M. (2026). Evolve: The operating model AI demands. Zen Ex Machina. https://zenexmachina.com/evolve/
- Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. https://scrumguides.org/scrum-guide.html