CAPM Agile Frameworks and Methodologies Practice Question
In Scrum, what is the purpose of the Sprint Retrospective?
⚠ Common exam trap
CAPM often tests the confusion between the four Scrum events — candidates frequently mix up the Sprint Review (product inspection with stakeholders) and the Sprint Retrospective (process inspection by the team).
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 and adapt the team's process.
The Sprint Retrospective is the Scrum event specifically designed for the team to inspect how they worked during the Sprint and identify improvements to their processes, tools, and interactions. It occurs after the Sprint Review and before the next Sprint Planning, and its output is typically one or more actionable improvement items added to the next Sprint Backlog. Its focus is on the 'how' (process and people), not the 'what' (product).
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 inspect and adapt the team's process.
Why this is correct
The Sprint Retrospective exists to inspect how the last Sprint went regarding individuals, interactions, processes, tools and Definition of Done, then adapt those elements. This directly satisfies the stem's focus on process improvement, distinguishing it from the Daily Scrum's daily inspection or the Sprint Review's product increment focus.
- ✗
To review the product increment with stakeholders.
Why it's wrong here
Reviewing the increment with stakeholders belongs to the Sprint Review, which inspects the product and gathers feedback. The retrospective instead examines how the team worked, covering processes, tools and interactions. Sprint Review would be correct when validating completed work against the Sprint Goal with customers and sponsors.
- ✗
To plan the work for the next sprint.
Why it's wrong here
Planning the next Sprint's work is Sprint Planning, where the team selects backlog items and defines the Sprint Goal. The retrospective instead inspects the team's collaboration and process, producing improvement actions for the next Sprint. Sprint Planning would be correct at the start of a Sprint, not at its close.
- ✗
To update the product backlog.
Why it's wrong here
Updating the product backlog is backlog refinement, an ongoing Product Owner activity, not the retrospective's remit. The retrospective inspects the team's processes and working agreements to produce improvement actions. It would be the right focus when grooming items ahead of Sprint Planning, not when closing out a Sprint.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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 PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI 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 CAPM exam.