CSM Scrum Events Practice Question
A Scrum Team has just completed the Sprint Review and is about to begin the Sprint Retrospective. The Scrum Master wants to confirm the purpose of the upcoming event. What is the primary purpose of the Sprint Retrospective?
⚠ Common exam trap
A common mix-up: candidates confuse the Retrospective with the Sprint Review, since both events inspect and adapt but focus on different subjects: one on the product, the other on the team's way of working.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
To inspect how the last Sprint went regarding individuals, interactions, processes, tools, and their Definition of Done, and to identify improvements.
The Sprint Retrospective is the final event of the Sprint and exists to inspect how the team worked across individuals, interactions, processes, tools, and the Definition of Done. The team identifies the most impactful improvements and may add them to the next Sprint Backlog. Product inspection and backlog adaptation belong to the Sprint Review, while goal setting and item selection belong to Sprint Planning.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To plan the Sprint Goal and select Product Backlog items for the next Sprint.
Why it's wrong here
Planning the Sprint Goal and selecting Product Backlog items happens in Sprint Planning, which opens the next Sprint. The Retrospective occurs at the end of the current Sprint and concentrates on process, interactions, tools, and environment. Mixing planning into the Retrospective would blur the event's focus and reduce the time available for genuine improvement.
- ✗
To inspect the Increment and adapt the Product Backlog based on stakeholder feedback.
Why it's wrong here
Inspecting the Increment and adapting the Product Backlog is the purpose of the Sprint Review, not the Sprint Retrospective. The Review focuses on the product and marketplace; the Retrospective focuses on how the team worked. Confusing the two events leads to a retrospective that drifts into product scope discussions instead of improving the team's way of working.
- ✗
To demonstrate the completed Increment to stakeholders and collect their feedback for the next Sprint.
Why it's wrong here
Demonstrating the Increment and gathering stakeholder feedback is the essence of the Sprint Review. The Retrospective is a private, team-focused event without stakeholders, aimed at improving the team's way of working. Treating the Retrospective as a demo would remove the safe space needed for candid reflection on process and collaboration.
- ✓
To inspect how the last Sprint went regarding individuals, interactions, processes, tools, and their Definition of Done, and to identify improvements.
Why this is correct
The Sprint Retrospective is the event where the Scrum Team inspects how the last Sprint went with respect to individuals, interactions, processes, tools, and the Definition of Done. Its purpose is to identify the most helpful changes to improve effectiveness and to agree on adaptations, which are often added to the next Sprint Backlog.
About these practice questions
One of 312 original CSM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scrum Alliance exam blueprint
This CSM practice question is part of Courseiva's free Scrum Alliance certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CSM exam.