CAPM Agile Frameworks and Methodologies Practice Question
An agile team has been running two-week Sprints for several months. During each Sprint Review, stakeholders provide feedback, but the team notices that the same concerns keep resurfacing and no one owns follow-up actions. The Scrum Master wants to ensure that the team inspects how it is working and adapts its process. Which Scrum event should the Scrum Master focus on to address this?
⚠ Common exam trap
Many exam-takers confuse the Sprint Review, which inspects the product Increment with stakeholders, with the Sprint Retrospective, which inspects the team's process and 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
✓
Sprint Retrospective
The Sprint Retrospective is the dedicated Scrum event for the team to inspect how it worked during the Sprint and adapt its process. Recurring concerns with no owner indicate a gap in process improvement, which is exactly what the Retrospective addresses. Sprint Review, Daily Scrum, and Sprint Planning serve product, daily coordination, and planning purposes respectively, so they do not provide the structured process-improvement focus required.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Daily Scrum
Why it's wrong here
The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is tactical and time-boxed for the current day's plan, not for deep process reflection. Using it to debate recurring retrospective-type concerns would dilute its focus and exceed its timebox, and it lacks the structure to produce owned improvement actions.
- ✓
Sprint Retrospective
Why this is correct
The Sprint Retrospective is the event where the team inspects how the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done. It is the only Scrum event specifically designed for the team to identify and address process improvements. Focusing here lets the team own follow-up actions on recurring concerns and adapt its way of working before the next Sprint begins.
- ✗
Sprint Review
Why it's wrong here
The Sprint Review is a working session where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog. Its purpose is product-focused: what was built and what to do next. While feedback is gathered here, it is not the event for inspecting and adapting the team's process, so it will not resolve the recurring internal concerns or assign ownership of process improvements.
- ✗
Sprint Planning
Why it's wrong here
Sprint Planning initiates the Sprint by laying out the work to be performed and defining the Sprint Goal. It focuses on what can be delivered and how the work will be achieved, not on inspecting the previous Sprint's process effectiveness. Addressing recurring concerns here would crowd out planning activities and does not provide the dedicated inspection-and-adaptation forum the team needs.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.