Sprint Retrospective

PSM I PSM I · Scrum Events

By Abu Anns · Last updated 20 November 2026Exam version: PSM I (Scrum Guide 2020)

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. It is the last event of the Sprint, timeboxed to a maximum of three hours for a one-month Sprint, and it is the one event that looks inward: instead of inspecting the product, the team inspects itself. The Scrum Team inspects how the last Sprint went with regard to individuals, interactions, processes, tools, and its Definition of Done. Inspected elements often vary with the domain of work — a team building medical software may focus on its testing process, while a team building a marketing site may focus on how it handles stakeholder requests — but the principle is the same: look honestly at how the Sprint went, and find the most helpful changes.

The Retrospective follows a clear logic. The team discusses what went well during the Sprint, what problems it encountered, and how those problems were solved — or not solved. Assumptions that led the team astray are identified and their origins explored: if the team assumed an integration would be simple and it was not, the Retrospective asks why that assumption was made and what would have caught it earlier. The team then identifies the most helpful changes to improve its effectiveness, and the most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint, which makes improvement work visible and planned rather than aspirational. This last point is tested on the exam: improvements are not vague resolutions, they are concrete changes that can be tracked as work.

Who attends the Retrospective? The Scrum Team — the Product Owner, the Scrum Master, and the Developers. The Product Owner's presence sometimes surprises people, because the Retrospective is often thought of as a Developers-only event, but the whole team inspects how the Sprint went, including the Product Owner's contribution. Stakeholders do not attend: the Retrospective is a safe space for the team to be honest about its own way of working, and outside observers would change the dynamic. The Scrum Master ensures the event takes place and is positive and productive, and often facilitates it — but the team as a whole owns the inspection and the improvements.

Retrospective vs Review

Candidates often confuse the Sprint Review and the Sprint Retrospective, and the exam exploits this. The Review inspects the product — the Increment, the outcome of the Sprint, progress toward the Product Goal — with stakeholders. The Retrospective inspects the process — individuals, interactions, processes, tools, and the Definition of Done — with the Scrum Team alone. The Review adapts the Product Backlog; the Retrospective adapts the team's way of working. A simple memory aid: Review looks outward at the product and the market, Retrospective looks inward at the team. If a question describes stakeholders giving feedback on the Increment, it is the Review. If it describes the team discussing why its estimates were off or why a handoff failed, it is the Retrospective.

Worked scenario

A Scrum Team's last Sprint was disrupted because a key dependency on another team was discovered late, forcing rework. At the Retrospective, the team discusses what happened: the dependency was not identified during refinement, and nobody checked with the other team until the work started. The team identifies two improvements: add a dependency check to refinement, and invite the other team's representative to Sprint Planning when shared work is involved. The most impactful improvement — the dependency check — is added to the next Sprint's Backlog as an explicit item so it actually happens. This is the Retrospective working as intended: honest inspection, root-cause thinking, concrete improvements, and follow-through. A team that holds a Retrospective, agrees everything was fine, and changes nothing has inspected without adapting — the exact failure the Guide warns about.

Making Retrospectives effective

A Retrospective is only as good as its honesty, and honesty needs safety. Team members must feel able to raise problems without fear of blame — which is why the Scrum Values of openness, courage, and respect matter most in this event. The Scrum Master creates that safety by facilitating well: keeping the discussion focused on the work and the process rather than on individuals, making sure every voice is heard, and preventing the event from becoming a complaint session with no outcomes. Techniques vary — some teams discuss what went well, what did not, and what to change; others focus on a single theme from the Sprint — but the structure matters less than the output. Every Retrospective should end with concrete improvements the team has committed to, with the most impactful ones addressed as soon as possible. A Retrospective that ends with good intentions and no actions has inspected without adapting, and the team will discuss the same problems again next Sprint. The Scrum Master also watches for patterns across Retrospectives: the same impediment appearing three Sprints in a row is a signal that the improvements are not being followed through, and the team needs to change its approach to acting on them.

What the Retrospective is not

The Retrospective is not a performance review, not a blame session, and not a status meeting. It does not evaluate individuals — it inspects how the team worked together, and the improvements it identifies are about the team's practices, tools, and interactions. It is also not optional: some teams skip the Retrospective when a Sprint went well, reasoning that there is nothing to fix. But a good Sprint still has lessons — what made it work, and how can the team repeat it? — and skipping the event removes the habit of inspection just when the team could learn the most from success. The Retrospective is the engine of the team's continuous improvement: without it, the team repeats the same Sprint indefinitely, and the same problems recur. With it, the team gets a little better every Sprint, and the improvements compound over time into a genuinely more effective team.

The Retrospective also covers the Definition of Done. The team inspects whether its quality standard is still right: is it too loose, letting defects through, or too strict, slowing delivery without adding value? As the team matures, the Definition of Done often becomes more demanding — more automation, more thorough testing, higher standards — and the Retrospective is where that evolution is discussed and agreed. A Definition of Done that never changes is a sign the team has stopped inspecting its own quality.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.What is the purpose of the Sprint Retrospective?

Report an error

Q2.What is the maximum timebox for the Sprint Retrospective for a one-month Sprint?

Report an error

Q3.During the Sprint Retrospective, the Scrum Team inspects how the last Sprint went with regard to which of the following?

Report an error

Q4.Who attends the Sprint Retrospective?

Report an error

Q5.A team identifies a valuable improvement during the Retrospective. According to the Scrum Guide, what may happen to it?

Report an error

Q6.During a Retrospective, the team realizes it assumed an integration would be simple, and that assumption caused a week of rework. What SHOULD the team do, according to the Scrum Guide?

Report an error

Q7.Which statement BEST distinguishes the Sprint Retrospective from the Sprint Review?

Report an error

Q8.A team holds a Retrospective, agrees everything went well, and identifies no improvements. What is the risk?

Report an error

Q9.When does the Sprint Retrospective take place?

Report an error