What is the goal of a sprint retrospective?
Tests if you see retrospectives as actionable process improvement, not just venting. A good answer defines the retro's purpose (inspecting the sprint's people, processes, tools) and explains how it creates concrete action items for the next sprint.
What's really being asked
This question checks if you understand the fundamental purpose of the Sprint Retrospective within the Scrum framework. It's not just about "doing Agile," but about understanding why this event exists. The interviewer is looking for your grasp of Scrum's empirical pillars: transparency, inspection, and adaptation. They want to see that you view the retrospective as a mechanism for process improvement, not just a forum for complaints. For a senior role, this extends to how you would facilitate or contribute to making them effective.
The full answer
A strong answer will hit three key points. First, define the purpose: the Sprint Retrospective is an opportunity for the Scrum Team to inspect itself. This inspection covers individuals, interactions, processes, tools, and their Definition of Done. Second, explain the outcome: the goal is to identify the most helpful changes to improve quality and effectiveness. The team creates a plan to implement these improvements during the next Sprint. At least one high-priority process improvement item is often added to the next Sprint Backlog. Third, connect it to continuous improvement: this inspect-and-adapt cycle applied to the team's own process is the literal engine of continuous improvement in Agile. It's how the team gets better over time, not just at building the product, but at working together.
The mistakes people make
A major red flag is describing the retrospective as a "blame game" or a complaint session. Answers that focus only on what went wrong without discussing what went well or, crucially, without mentioning the creation of concrete, actionable improvement items are weak. Another mistake is treating the retro's output as mere suggestions rather than a committed plan. A senior candidate should know that the most impactful improvements are often added to the next Sprint Backlog to ensure they are actually worked on. Saying it's "the Scrum Master's meeting" is also incorrect; it's an event for the entire Scrum Team.
What usually comes next
Be prepared for "How would you handle a retrospective where no one speaks up?" or "What if the same problems come up every retro without being solved?". Another common one is, "Describe a specific, impactful improvement that came out of a retrospective you were in." These questions probe your practical experience and leadership in making the theory work in reality.
A concrete example
In a past project, our CI/CD pipeline was taking over 45 minutes to run, which delayed feedback on pull requests. During a retrospective, we identified this as a major bottleneck. Instead of just complaining, we created a specific action item for the next sprint: "Investigate and reduce CI pipeline execution time." We allocated 8 story points for this task. The following sprint, two engineers paired on it and discovered redundant test suites. They parallelized the remaining jobs, cutting the average pipeline time to under 15 minutes. This single, retro-driven improvement significantly increased our team's velocity and morale for all subsequent sprints.
Interview question
What is the primary goal of a Sprint Retrospective within the Scrum framework?
- a.To identify what went wrong during the sprint and assign responsibility for those issues.
- b.To ensure the Scrum Master has a clear understanding of team dynamics and individual performance.
- c.To review the completed product increment with stakeholders and gather their feedback.
- d.To inspect the team's process and create actionable plans for continuous improvement in the next sprint.Correct
Why? this is the answer
The Sprint Retrospective's core purpose is for the Scrum Team to inspect its process (people, interactions, tools) and create concrete, actionable plans for improvement in the upcoming sprint, driving continuous improvement. Option A is a common misconception, as the retrospective is not a forum for assigning blame but for collective learning and adaptation.
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