Who attends the Sprint Retrospective?

The entire Scrum Team: Product Owner, Scrum Master, and Developers.

Empiricism in Scrum (canonical phrase)

Scrum is founded on empiricism and lean thinking.

Areas commonly improved in Retrospectives

Processes, tools, relationships, communication, skills, and the Definition of Done.

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

Sprints are the heartbeat of Scrum, where ideas are turned into value.

An Increment is a concrete stepping stone toward the Product Goal.

Sprint Retrospective: Continuous Improvement for the Scrum Team — Professional Scrum Master I (PSM I) Complete Exam-Ready Mastery Course

Sprint Retrospective: Where the Scrum Team Improves Itself

Why This Event Matters

The Sprint Retrospective is where the Scrum Team inspects how it works, chooses concrete improvements, and strengthens how it lives the Scrum values.

Link to Other Events

Daily Scrum adapts the plan, Sprint Review adapts the Product Backlog, and the Retrospective adapts the way the Scrum Team collaborates and delivers.

Exam Focus

You must know the Retrospective’s purpose, timebox, attendees, how it supports empiricism, and how to spot healthy vs. unhealthy practices in scenarios.

Purpose, Timebox, and Attendees: The Core Facts

Purpose in One Sentence

The Sprint Retrospective lets the Scrum Team inspect itself and create a plan for improvements to be enacted during the next Sprint.

What Is Inspected?

The team inspects processes, tools, skills, collaboration, quality practices, communication, and the Definition of Done, not the product backlog items.

Timebox to Remember

For a one‑month Sprint, the Retrospective is timeboxed to a maximum of 3 hours; shorter Sprints usually mean shorter Retrospectives.

Who Attends?

The entire Scrum Team attends: Product Owner, Scrum Master, and Developers. Managers and stakeholders are not standard attendees.

Where the Retrospective Fits in the Sprint

Place in the Sprint

The Sprint Retrospective happens after the Sprint Review and before the next Sprint Planning, as part of the ending Sprint.

No Gaps Between Sprints

There is no gap between Sprints; the Retrospective is inside the Sprint, and the next Sprint starts immediately after the previous one ends.

Three Inspect-and-Adapt Loops

Daily Scrum adapts the plan, Sprint Review adapts the Product Backlog, and the Retrospective adapts how the Scrum Team works.

Skipping Is an Anti-Pattern

Skipping the Retrospective because “nothing to improve” breaks empiricism and continuous improvement and is not aligned with Scrum.

Empiricism and Continuous Improvement in the Retrospective

Empiricism in Action

Empiricism means inspecting real data and experiences from the Sprint, reflecting on causes, and adapting with concrete experiments.

Continuous Improvement Loop

Each Sprint should produce at least one improvement action that is carried into the next Sprint and revisited in the next Retrospective.

Common Focus Areas

Teams often inspect process, tools, relationships, and the Definition of Done, looking for small but meaningful improvements.

Exam Signal

Retrospectives with no data, no specific actions, or no follow‑up are weak on empiricism and are poor practices in exam scenarios.

A Walkthrough of a 90‑Minute Sprint Retrospective

Setting the Stage

The Scrum Master opens the Retrospective, emphasizes safety and focus on improvement, and runs a quick check‑in to build openness.

Gathering Data

The team builds a Sprint timeline with key events and reviews metrics like items done, items not done, and defects discovered.

Generating Insights

They cluster issues such as testing bottlenecks and unclear criteria, then discuss patterns and root causes together.

Choosing Actions

They select two specific improvements: a WIP limit and a shared refinement session, and add them to the next Sprint Backlog.

Closing Positively

The team ends by sharing appreciations, reinforcing courage, respect, and commitment to working better together.

Scrum Values in the Retrospective

Commitment and Focus

The team shows commitment by improving how it works and focus by selecting a small, realistic set of improvements for the next Sprint.

Openness and Respect

Members share successes and problems honestly, listen without blame, and respect different perspectives and constraints.

Courage

Courage appears when the team surfaces uncomfortable truths and challenges unhelpful patterns in a constructive way.

Exam Lens

In scenarios, look for options that increase openness, respect, and focus on improvement; avoid those that blame or silence people.

Thought Exercise: Turning Complaints into Improvements

Work through this exercise to practice turning vague complaints into actionable improvements, a key Retrospective skill.

Imagine you are the Scrum Master. In the Retrospective, you hear these raw comments:

“Testing is always a mess at the end of the Sprint.”
“Stakeholders keep changing their minds.”
“Our Daily Scrum feels like a boring status meeting.”

Your task: For each comment, rewrite it as a clear problem statement and propose one concrete improvement that could be added to the next Sprint.

Use this pattern:

Problem statement: “We observe that …, which leads to …”
Improvement idea: “Next Sprint, we will try … so that …”

Try it yourself before looking at the sample answers below.

---

Sample transformations (compare with your own):

Testing

Problem: “We observe that most testing happens in the last two days of the Sprint, which leads to rushed work and escaped bugs.”
Improvement: “Next Sprint, we will limit ourselves to 2 PBIs in progress and only start new work when existing items are fully tested, so that testing is spread more evenly.”

Stakeholders changing minds

Problem: “We observe that stakeholders often introduce new ideas during the Sprint, which leads to interruptions and unfinished work.”
Improvement: “Next Sprint, we will ask stakeholders to bring new ideas to Sprint Review and refinement, and we will keep the Sprint Goal stable, so that the team can focus.”

Daily Scrum

Problem: “We observe that the Daily Scrum is used to report to the Scrum Master, which leads to low engagement and little adaptation.”
Improvement: “Next Sprint, the Developers will facilitate the Daily Scrum themselves and use the Sprint Goal as the central question, so that we adapt our plan instead of reporting status.”

Quiz 1: Core Facts About the Sprint Retrospective

Test your understanding of purpose, timebox, and attendees.

Which statement best describes the Sprint Retrospective according to Scrum?

A meeting where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog.
An optional event where the Scrum Master collects status updates from Developers at the end of the Sprint.
An event for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
A meeting for managers to evaluate the performance of individual Developers and assign bonuses.

Show Answer

Answer: C) An event for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The Sprint Retrospective is defined as an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. Stakeholders are part of the Sprint Review, not the Retrospective. It is not optional, not a status meeting, and not a performance review.

Quiz 2: Identifying Effective and Ineffective Practices

Apply what you know to a scenario.

A Scrum Team has a one‑month Sprint. Over several Sprints, they have decided to skip the Sprint Retrospective because they "already know what to improve" and feel they are too busy. What is the best assessment?

This is acceptable if the team is mature and has stable processes.
This violates Scrum because the Sprint Retrospective is a formal event for inspection and adaptation every Sprint.
This is fine as long as the Scrum Master holds a private Retrospective with the Product Owner.
This is recommended, because Retrospectives slow down delivery and are not needed when velocity is high.

Show Answer

Answer: B) This violates Scrum because the Sprint Retrospective is a formal event for inspection and adaptation every Sprint.

The Sprint Retrospective is one of Scrum’s five events and is held every Sprint. It enables empiricism and continuous improvement. Skipping it, even for a "mature" team, is not aligned with Scrum. Private meetings between Scrum Master and Product Owner do not replace the Retrospective.

Key Terms and Facts Review

Use these flashcards to reinforce core concepts about the Sprint Retrospective and related Scrum elements.

Sprint Retrospective – main purpose: An opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
Sprint Retrospective – timebox for a 1‑month Sprint: Maximum of 3 hours.
Who attends the Sprint Retrospective?: The entire Scrum Team: Product Owner, Scrum Master, and Developers.
Empiricism in Scrum (canonical phrase): Scrum is founded on empiricism and lean thinking.
Areas commonly improved in Retrospectives: Processes, tools, relationships, communication, skills, and the Definition of Done.
Definition of Done (canonical): The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
How often is the Sprint Retrospective held?: Once every Sprint, after the Sprint Review and before the next Sprint Planning.
Typical exam trap about attendees: Treating the Product Owner as optional or running the Retrospective only with Developers or managers is incorrect.

From Insight to Action: Making Improvements Stick

Make Actions Visible

Turn improvement ideas into visible items in the Sprint Backlog or Product Backlog so they are owned and tracked.

Balance Work and Improvement

The Scrum Team decides how much capacity to invest in improvements, often choosing a small, steady flow of changes each Sprint.

Inspect the Experiment

In the next Retrospective, the team checks whether the chosen improvements actually helped and adapts again.

Exam Hint

Prefer answers where at least one improvement is implemented in the very next Sprint, not postponed indefinitely.

Common Anti‑Patterns and Exam Traps

Status and Blame

If the Retrospective becomes a status report or a place to blame people, it is not aligned with Scrum’s purpose or values.

Skipping or Rushing

Skipping the event or reducing it to a token few minutes breaks empiricism and weakens continuous improvement.

No Actions, No Impact

A Retrospective without clear, concrete improvement actions fails its core purpose of planning change for the next Sprint.

Include the Whole Scrum Team

Leaving out the Product Owner or Scrum Master undermines the idea that the Scrum Team as a whole inspects and improves itself.

Key Terms

Scrum: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Sprint: Sprints are the heartbeat of Scrum, where ideas are turned into value.
Increment: An Increment is a concrete stepping stone toward the Product Goal.
Developers: Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
Scrum Team: The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
empiricism: Scrum is founded on empiricism and lean thinking.
Sprint Goal: The Sprint Goal is the single objective for the Sprint.
Product Goal: The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
Scrum Master: The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
Scrum values: The five values of Scrum are Commitment, Focus, Openness, Respect, and Courage; they guide the behavior of the Scrum Team and are especially visible during events like the Sprint Retrospective.
Product Owner: The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Sprint Backlog: The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
Product Backlog: The Product Backlog is an emergent, ordered list of what is needed to improve the product.
Definition of Done: The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
Sprint Retrospective: A Scrum event held after the Sprint Review and before the next Sprint Planning, where the Scrum Team inspects itself and creates a plan for improvements to be enacted during the next Sprint.