What is the output of a Sprint Retrospective, and what happens next?

WHAT THIS TESTS: This question tests whether you view Agile ceremonies as valuable, outcome-driven events or simply meetings to attend. The interviewer is probing your ability to translate discussion into concrete, prioritized work. They are listening for a bias toward action and a clear understanding that the retrospective's goal is to make the next sprint better, not just to document the last one.

A GOOD ANSWER COVERS: First, the official output is a plan for implementing improvements to increase the team's quality and effectiveness. This is a forward-looking plan, not a historical record.

Second, the most critical immediate action is that the most impactful improvement(s) are added to the Sprint Backlog for the very next Sprint. This ensures the improvement is treated as real, accountable work.

Third, the entire Scrum Team commits to this improvement item. It is not a side-task or something for the Scrum Master to chase; it's part of the team's shared commitment.

Fourth, a senior answer will mention the broad scope of potential improvements, which can cover anything from people and interactions to processes, tools, or even refining the Definition of Done.

COMMON WRONG ANSWERS: "The output is meeting notes" or "a list of what went wrong." This is a major red flag. It shows a passive, non-action-oriented view. The goal is a plan, not a history report.

"We create tickets for the improvements." This is better, but incomplete. The follow-up question is, "Where do those tickets go?" If they land in a separate, unprioritized backlog that is rarely visited, the retrospective was a waste of time. The key is adding them to the next Sprint Backlog.

"The Scrum Master is responsible for following up." This is incorrect. While the Scrum Master facilitates the process, the entire Scrum Team owns the implementation of the improvements. It is a shared responsibility.

LIKELY FOLLOW-UPS: "Give me a concrete example of a retrospective improvement you added to a sprint." "What happens if the team identifies several 'most impactful' improvements? How do you decide which one to add to the sprint?" "What do you do if the team consistently fails to complete its retrospective improvement items during the sprint?"

ONE CONCRETE EXAMPLE: Problem: During a sprint, the team found that CI builds were taking over 45 minutes, frequently breaking developer concentration and slowing down verification.

Retrospective Output: The team agreed the build time was the most impactful issue to address.

Immediate Action: A story was created, estimated, and added to the next Sprint Backlog: "Parallelize test suites in CI pipeline to reduce full build-and-test time to under 20 minutes." This item was then treated as a core part of the sprint commitment, not an optional task.