Try 10 focused CSM questions on Scrum Foundations & Agile Mindset, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | CSM |
| Topic area | Scrum Foundations & Agile Mindset |
| Blueprint weight | 18% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Scrum Foundations & Agile Mindset for CSM. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 18% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Scrum Foundations & Agile Mindset
During a Sprint, the Scrum Team learns that a new security constraint affects one Product Backlog item selected for the Sprint. The Sprint Goal is still achievable with the other items.
Stakeholders ask to see “everything the team worked on” at the Sprint Review to reassure themselves, even if some work is not finished.
Which option best optimizes transparency and predictability while staying within Scrum rules for artifacts and commitments?
Best answer: C
What this tests: Scrum Foundations & Agile Mindset
Explanation: An Increment is only the work that meets the Definition of Done, which preserves transparency and predictability. The Sprint Goal remains the Sprint’s commitment unless it becomes obsolete, and any undone work is adapted by returning it to the Product Backlog. The Product Goal provides the longer-term context for re-ordering what to do next.
In Scrum, the Increment is the sum of all Product Backlog items completed during a Sprint plus prior Increments, and it must meet the Definition of Done. Showing only Done work at the Sprint Review keeps the artifact transparent: stakeholders can trust what is truly usable.
When new information emerges mid-Sprint, the Scrum Team adapts without breaking core constraints:
The key is to be explicit about what is Done versus in-progress, rather than redefining “Increment” or weakening the Definition of Done to satisfy a demo request.
Only Done work is part of the Increment, while the Sprint Goal and Product Goal guide what to finish now and what to re-plan next.
Topic: Scrum Foundations & Agile Mindset
A Scrum Team is working toward the Product Goal: “Reduce customer support calls through self-service account recovery.”
For the current Sprint, the Sprint Goal is: “Customers can reset their password without calling support.”
Midway through the Sprint, Developers have a password reset screen working in a branch, but it has not been integrated, security-checked, or tested as required by the Definition of Done. The Product Owner wants to present it at the Sprint Review as the new Increment.
What is the most Scrum-aligned response?
Best answer: C
What this tests: Scrum Foundations & Agile Mindset
Explanation: In Scrum, an Increment is a concrete step toward the Product Goal that is usable and meets the Definition of Done. Since the password reset work has not met the Definition of Done, it cannot be represented as an Increment. The best response is to maintain transparency and inspect/adapt plans while keeping the Sprint Goal as the focus for the Sprint.
The decisive factor is that the work does not meet the Definition of Done. In Scrum, only work that meets the Definition of Done contributes to a usable Increment; anything else is incomplete and must be made transparent as work in progress.
The Product Owner can still use the Sprint Review to inspect progress toward the Product Goal and gather feedback, but should not mislabel unfinished work as an Increment. The Scrum Team should keep working toward the Sprint Goal, updating the Sprint Backlog as needed to finish to the Definition of Done.
Acceptance by the Product Owner does not replace the Definition of Done as the quality bar for an Increment.
An Increment is only created when work meets the Definition of Done, so this is still work in progress.
Topic: Scrum Foundations & Agile Mindset
A Scrum Team runs 2-week Sprints, but work is split into phases: Sprint 1 “requirements,” Sprint 2 “design,” Sprint 3 “build,” and Sprint 4 “test.” Stakeholders only see a demo at the end of Sprint 4, and feedback is handled as a change request for the next release.
Which Scrum concept best maps to the correction that restores regular inspection and adaptation of the product?
Best answer: D
What this tests: Scrum Foundations & Agile Mindset
Explanation: “Waterfall in Sprints” delays learning by postponing real product inspection until a later phase or release. The Scrum concept that directly restores inspection and adaptation at least every Sprint is the Sprint Review, where stakeholders inspect a Done Increment and the Product Backlog is adapted based on what was learned.
The situation describes “waterfall in Sprints”: analysis, design, build, and test are separated across multiple Sprints, which prevents producing a usable Increment and delays feedback. Scrum relies on empiricism, so the team should create a Done Increment every Sprint and use the Scrum event designed for product inspection and adaptation.
In the Sprint Review, the Scrum Team and stakeholders inspect what was accomplished, discuss what to do next, and adapt the Product Backlog based on feedback and current conditions. This short feedback loop is what replaces “end-of-project” change requests with ongoing learning and adjustment. A status-style meeting without a Done Increment misses the purpose.
Other events can help execution, but they don’t replace the product-level inspection/adaptation mechanism of the Sprint Review.
The Sprint Review is the event to inspect the Increment with stakeholders each Sprint and adapt the Product Backlog based on feedback.
Topic: Scrum Foundations & Agile Mindset
Midway through a Sprint, the Product Owner is unavailable. A stakeholder asks the Scrum Master to “re-prioritize” a new request. The Scrum Master changes the Product Backlog order and tells the Developers to switch to the new item immediately, even though the Sprint Goal is about improving the onboarding flow.
What is the most likely near-term impact?
Best answer: D
What this tests: Scrum Foundations & Agile Mindset
Explanation: The Product Owner is accountable for maximizing value and ordering the Product Backlog, while Developers manage the Sprint Backlog to meet the Sprint Goal. When the Scrum Master assumes Product Owner decisions and redirects work mid-Sprint, the team’s focus shifts and Sprint Goal progress becomes harder to inspect and more likely to slip.
Scrum has three accountabilities with distinct focus: the Product Owner maximizes value and orders the Product Backlog, the Developers create a usable Increment and adapt the Sprint Backlog to meet the Sprint Goal, and the Scrum Master is accountable for Scrum’s effectiveness. In this scenario, the Scrum Master steps into Product Owner work by reordering the Product Backlog and directing a mid-Sprint switch. That disrupts the Developers’ plan toward the Sprint Goal and makes it less transparent what the Sprint is trying to achieve and how close the team is to achieving it. The near-term consequence is reduced ability to inspect Sprint Goal progress and an increased risk of not meeting the Sprint Goal. A Scrum Master should instead help re-establish the proper accountability and facilitate engagement with the Product Owner.
By taking over Product Owner focus (value and ordering), the Scrum Master creates churn that obscures and jeopardizes Sprint Goal progress.
Topic: Scrum Foundations & Agile Mindset
Midway through a Sprint, stakeholders ask the Scrum Team for evidence that the product is making real, usable progress toward the Sprint Goal and ultimately the Product Goal.
Which indicator is the best evidence in Scrum that progress and quality are being validated?
Best answer: B
What this tests: Scrum Foundations & Agile Mindset
Explanation: In Scrum, the most reliable validation of progress and quality is a Done Increment: working product that meets the Definition of Done. If it advances the Sprint Goal, it provides transparent evidence of progress toward the Product Goal through usable outcomes, not activity or plans.
Scrum validates progress and quality through outcomes that can be inspected. The Increment is the concrete artifact that provides this transparency, and it only counts as an Increment when it meets the Definition of Done (quality baseline). When the Done Increment advances the Sprint Goal, it is strong evidence that the Scrum Team is making usable progress toward the Product Goal.
Measures or approvals about activity, plans, or predictions can be informative, but they do not validate that the product is working and meets the agreed quality standard. The key takeaway is that “Done, usable product” is the primary indicator, not effort-based completion or document sign-offs.
A Done Increment is usable, meets the Definition of Done, and is the primary evidence of value and quality toward the Sprint Goal (and Product Goal).
Topic: Scrum Foundations & Agile Mindset
Which Scrum event is specifically intended to integrate stakeholders by inspecting the Increment and adapting the Product Backlog, without interrupting the Developers’ day-to-day work during the Sprint?
Best answer: C
What this tests: Scrum Foundations & Agile Mindset
Explanation: The Sprint Review is the primary Scrum event for engaging stakeholders. It creates a regular, timeboxed opportunity to inspect the Increment together and adjust what to do next by updating the Product Backlog, rather than injecting ad-hoc requests into the Sprint. This supports focus while still enabling frequent feedback and adaptation.
In Scrum, stakeholder input is integrated most effectively through the Sprint Review. Its purpose is to inspect the outcome of the Sprint (the Increment) with stakeholders and decide what adaptations make sense, typically by adjusting the Product Backlog to maximize value.
By using the Sprint Review as the main feedback loop, the Scrum Team avoids disrupting the Sprint with unscheduled direction changes and preserves focus on the Sprint Goal, while still practicing transparency, inspection, and adaptation at least every Sprint. The Daily Scrum and Sprint Retrospective are primarily for the Scrum Team, and Sprint Planning is for setting the Sprint Goal and plan for the upcoming Sprint.
The Sprint Review is where the Scrum Team and stakeholders inspect the Increment and collaboratively adapt the Product Backlog based on what was learned.
Topic: Scrum Foundations & Agile Mindset
A Scrum Team selects a Sprint Goal: “Customers can reset their password.” During Sprint Planning, the Developers slice the work into separate Product Backlog Items by technical layer (database changes, API endpoint, UI screen), intending to integrate “at the end of the Sprint.”
What is the most likely near-term impact of this slicing decision?
Best answer: D
What this tests: Scrum Foundations & Agile Mindset
Explanation: Slicing by technical layers tends to produce “almost done” parts that do not meet the Definition of Done as a usable Increment. That reduces transparency because completed tasks don’t reliably indicate progress toward the Sprint Goal. The near-term consequence is higher risk of finishing the Sprint without a Done, valuable Increment to inspect.
Vertical slicing aims to deliver small, end-to-end pieces of value that can meet the Definition of Done and contribute to a usable Increment. When work is split by layers (DB, API, UI) and integrated late, the Sprint can accumulate partial components that are not “Done” in a way users can experience. That makes it difficult to inspect real progress toward the Sprint Goal, because task completion (e.g., “API done”) does not equal a working password-reset capability. A better slice would be a thin, integrated “reset password” flow (even minimal) that can be demonstrated and potentially released, then expanded in subsequent slices.
Layer-based slicing can create lots of partial work without a usable, integrated Increment, making true progress toward the Sprint Goal hard to see.
Topic: Scrum Foundations & Agile Mindset
Mid-Sprint, a stakeholder brings an urgent request. The Developers believe they can still meet the Sprint Goal if they swap out some Sprint work and make the change visible to everyone.
Which Scrum term best matches the artifact that is updated during the Sprint to reflect this emergent work while keeping transparency toward the Sprint Goal?
Best answer: A
What this tests: Scrum Foundations & Agile Mindset
Explanation: Emergent work discovered during a Sprint is made transparent by updating the Sprint Backlog, which is the Developers’ plan for how they will achieve the Sprint Goal. It can be adapted throughout the Sprint as new information appears, while keeping the Sprint Goal intact. This keeps inspection and adaptation visible to the Scrum Team and stakeholders.
The Sprint Backlog is the artifact that provides transparency into the work planned and the work that emerges during the Sprint. It contains the Sprint Goal, the selected Product Backlog Items, and the plan for delivering them, and it is updated by the Developers throughout the Sprint as more is learned. When an urgent request arises, the Scrum Team can collaborate to negotiate scope (for example, swapping items) as long as the Sprint Goal remains viable, and the updated Sprint Backlog makes the change explicit and inspectable. The key is that adaptation happens openly in the Sprint Backlog rather than being handled “off the books.”
The Sprint Backlog is the Developers’ evolving plan for the Sprint and is updated as more is learned while working toward the Sprint Goal.
Topic: Scrum Foundations & Agile Mindset
A Scrum Team works in 2-week Sprints on a customer portal. Each Sprint is run as mini-phases: week 1 “requirements and design,” week 2 “build and test.” Stakeholders attend the Sprint Review mainly to approve documents, and the product isn’t usable until several Sprints later.
Which recommendation should the Scrum Master NOT make if the goal is to move away from “waterfall in Sprints” and restore inspection and adaptation?
Best answer: C
What this tests: Scrum Foundations & Agile Mindset
Explanation: “Waterfall in Sprints” shows up when work is broken into sequential phases and decisions are locked in early, limiting learning. Adding a “design complete” gate and freezing change increases batch size and delays feedback, undermining empiricism. Restoring inspection and adaptation requires producing a Done Increment and using events to re-plan based on what is learned.
The core issue is a phase-driven approach that delays a usable, Done Increment and turns the Sprint Review into a document sign-off. Scrum relies on empiricism, so teams need frequent transparency into working results, followed by inspection and adaptation.
To correct “waterfall in Sprints,” aim to:
Adding a mid-Sprint gate and freezing change pushes the team back toward predictive control, reducing feedback and adaptability.
Phase gates and freezing change reinforce sequential handoffs and reduce opportunities to inspect results and adapt within and across Sprints.
Topic: Scrum Foundations & Agile Mindset
Midway through a Sprint, stakeholders ask the Product Owner for frequent status updates and want to suggest changes immediately. The Scrum Master wants to integrate stakeholders effectively without derailing the Developers’ focus.
Which option is the best evidence to validate progress, quality, and value while keeping stakeholder involvement appropriately timed in Scrum?
Best answer: C
What this tests: Scrum Foundations & Agile Mindset
Explanation: In Scrum, the strongest validation of progress, quality, and value is a usable Increment that meets the Definition of Done. The Sprint Review is designed to involve stakeholders in inspecting outcomes and adapting the Product Backlog based on what was actually achieved, without disrupting the Developers during the Sprint.
To integrate stakeholders without derailing the Scrum Team, use the event and artifact intended for empirical feedback: the Sprint Review and the Increment. A Done Increment provides the most reliable evidence because it is working product that meets the Definition of Done (quality) and can be inspected against the Sprint Goal and Product Goal (progress and value). Stakeholders can then give feedback and collaborate with the Product Owner on what to do next via Product Backlog adaptation, rather than injecting ad-hoc direction into the Sprint’s work. Measures and activity outputs can support transparency, but they do not validate value and quality as directly as a Done Increment.
A Done Increment inspected at the Sprint Review provides transparent evidence of value and quality and enables feedback without interrupting the Sprint.
Use the CSM Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the CSM guide on PMExams.com, then return to PM Mastery for timed practice.