What is the Sprint Retrospective output and what happens next?
Whether you see Retrospectives as adaptation events or venting.
Output is a concrete improvement plan enacted in the next Sprint, not parked.
Calling the output feedback with no action mechanism.
What's really being asked
This question tests whether you understand the empirical purpose of Scrum events. The guide states that Scrum events are designed to provoke change and that inspection without adaptation is considered pointless. A Retrospective is not a documentation exercise; it is an inspection point that exists to drive immediate process changes.
A GOOD ANSWER COVERS four things in order. First, the primary output is a concrete plan for improvements. The team inspects how the last Sprint went. Second, the output must be actionable, not vague observations. Third, these improvements must be enacted in the next Sprint. The guide emphasizes adaptation: if aspects of the process deviate outside acceptable limits, they must be adjusted. Fourth, the team should identify the most impactful changes and commit to them immediately rather than deferring them.
COMMON WRONG ANSWERS include three red flags. One: describing the output as feedback or lessons learned without a mechanism for change. Two: saying items go into a parking lot or are discussed later, which violates the principle that adaptation should happen immediately. Three: treating the event as blame-oriented rather than system-oriented; the guide focuses on improving the system of work.
LIKELY FOLLOW-UPS include these angles. How do you prevent the same improvement from appearing in every Retrospective? How do you balance process improvements against Sprint work? What happens if the team identifies an adaptation that requires support beyond the team?
A concrete example
A team notices that delayed code reviews caused a bottleneck in the last three Sprints. The Retrospective output is not that code reviews were slow. It is a specific plan: enforce a twenty-four-hour review turnaround, trial a pairing rotation, and measure the result in the next Sprint. This plan is treated as work to be done immediately in the upcoming Sprint, not as a suggestion for the future.
Interview question
Which best describes the Scrum Guide's view of a Sprint Retrospective output and its immediate next step?
- a.A blame-oriented review identifying which team members caused process deviations
- b.A set of improvement ideas placed in a parking lot for discussion in a future Retrospective
- c.A feedback summary of lessons learned without a defined mechanism to drive change
- d.A concrete plan for process improvements enacted in the next SprintCorrect
Why? this is the answer
The Scrum Guide requires the Retrospective to produce a concrete improvement plan that is enacted in the next Sprint. Option B is tempting because teams often backlog process ideas, but deferring adaptations violates the empirical principle that inspection without adaptation is pointless.
Just read this? Test yourself on what you have been reading.
Read the original → scrumguides.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles