Answering: “A Sprint Retrospective should be held:”

The Sprint Retrospective is held at the end of every Sprint. It is the last event of the Sprint, not an optional meeting or a project wrap-up.

Exam Question

A Sprint Retrospective should be held: (choose the best answer)

A. At the end of each Sprint.
B. At the end of the last Sprint in a project or a release.
C. At the beginning of each Sprint.
D. Only when the Scrum Team determines it needs one.

Correct Answer

A. At the end of each Sprint.

Why This Is the Correct Answer

The Scrum Guide states that “The Sprint Retrospective concludes the Sprint.” Its purpose is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regard to individuals, interactions, processes, tools and its Definition of Done. Because every Sprint produces new experience, every Sprint ends with a Retrospective. Holding it regularly keeps improvement small and continuous. The timebox is a maximum of three hours for a one-month Sprint and usually shorter for shorter Sprints. The most helpful improvements may even be added to the Sprint Backlog for the next Sprint.

Why the Other Options Are Wrong

B. At the end of the last Sprint of a project or release. That turns a Sprint event into a lessons-learned session at the end. The team would lose many chances to improve along the way.

C. At the beginning of each Sprint. Sprint Planning starts a Sprint. The Retrospective looks back at a Sprint that has just been completed.

D. Only when the team decides it needs one. All Scrum events are required. Skipping the Retrospective removes a formal opportunity to inspect and adapt.

Exam Tip

Scrum events have fixed places in the Sprint. If an option makes an event optional or ties it to a project milestone, eliminate it.

Key Takeaways

• Every Sprint ends with a Sprint Retrospective.
• Its purpose is to improve quality and effectiveness.
• No Scrum event is optional.