Skip to content
PMPCAPM

Sprint Retrospective

The Sprint Retrospective is a Scrum event where the Scrum Team inspects how the last Sprint went with regard to people, relationships, processes, and tools, and creates a plan for improvements.

Share:

Know it well enough for the exam? Questions on Sprint Retrospective are scenario-based, not definitional.

Practice it free

Explanation

The Sprint Retrospective is the final event of a Sprint and occurs after the Sprint Review. The Scrum Team identifies the most helpful changes to improve its effectiveness and addresses them as soon as possible. Improvements may be added to the Sprint Backlog for the next Sprint.

During the retrospective, the team discusses what went well, what did not go well, and what improvements can be made. Common formats include Start-Stop-Continue, Mad-Sad-Glad, and the sailboat metaphor. The Scrum Master facilitates the session and ensures it remains constructive and safe for honest feedback.

The Sprint Retrospective is timeboxed to three hours for a one-month Sprint. It is a key mechanism for continuous improvement and is one of the most important events in Scrum. Teams that skip or shortchange retrospectives tend to stagnate and accumulate process debt.

Key Points

  • •Focuses on process improvement, not the product
  • •Identifies what went well, what to improve, and actionable changes
  • •Timeboxed to three hours for a one-month Sprint
  • •Improvement items can be added to the next Sprint Backlog

Exam Tip

The retrospective is about the process, not the product. If a question asks about improving how the team works, the Sprint Retrospective is the answer.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Part of

Agile & Hybrid

Study full domain →

Practice Sprint Retrospective

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.