Try 10 focused CSM questions on Scrum Master as Servant Leader, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | CSM |
| Topic area | Scrum Master as Servant Leader |
| Blueprint weight | 23% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Scrum Master as Servant Leader 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: 23% 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 Master as Servant Leader
Midway through a Sprint, several stakeholders complain they “never know what’s going on” and ask the Scrum Master to start sending a detailed weekly status report and to let them join the Daily Scrum “so we can redirect work sooner.” The Product Owner asks the Scrum Master to educate the stakeholders on how to work with the Scrum Team.
What should the Scrum Master ask or verify FIRST before deciding how to educate them?
Best answer: C
What this tests: Scrum Master as Servant Leader
Explanation: Start by understanding what problem the stakeholders are trying to solve (visibility, decision-making cadence, ability to provide feedback) and what information they need to collaborate effectively. With that clarified, the Scrum Master can teach how Scrum already provides transparency and the right touchpoints (especially the Sprint Review) without disrupting the Developers’ Daily Scrum.
As a servant-leader, the Scrum Master educates stakeholders by first clarifying their needs and the collaboration outcome they want. In this scenario, the request to join the Daily Scrum and demand extra reporting signals a possible mismatch between stakeholder expectations and Scrum’s intended feedback loops. Before proposing training content or changes, the Scrum Master should learn what decisions stakeholders need to make, what transparency is missing, and what timing would make feedback useful.
From there, the Scrum Master can coach toward Scrum-appropriate mechanisms, for example:
The key is to address the underlying need, not to accept a solution that assumes new controls or roles.
Clarifying the stakeholders’ actual need and timing lets the Scrum Master teach the most relevant Scrum expectations and collaboration points.
Topic: Scrum Master as Servant Leader
During a Sprint, the Scrum Master notices the Daily Scrum has become a status meeting. Each Developer takes turns facing the Scrum Master and answering “what I did/yesterday, what I’ll do today, blockers,” with little discussion between Developers. Afterward, coordination happens in side conversations and the Sprint Goal is rarely mentioned.
What is the best next step for the Scrum Master?
Best answer: A
What this tests: Scrum Master as Servant Leader
Explanation: The Daily Scrum is for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog plan for the next day. When it turns into reporting to the Scrum Master, the Scrum Master should coach the Developers to self-manage the event and collaborate on a shared plan. Refocusing on the Sprint Goal restores empiricism and reduces the need for side meetings.
In Scrum, the Daily Scrum is an event for the Developers. Its purpose is to inspect progress toward the Sprint Goal and adapt the plan in the Sprint Backlog for the next 24 hours. When people “report” to the Scrum Master, transparency and collaboration suffer because the team optimizes for looking busy instead of jointly planning the day.
A useful next step is to coach and facilitate a shift such as:
The key is changing the interaction from individual status reporting to shared inspection and adaptation of the work.
This corrects the reporting anti-pattern by returning ownership to the Developers and refocusing the event on inspecting progress and adapting the plan for the next 24 hours.
Topic: Scrum Master as Servant Leader
Mid-Sprint, the Scrum Team is working toward the Sprint Goal: “Users can reset passwords end-to-end.” In the Daily Scrum, one Developer says the UI layout work is taking longer than expected. Another says the team cannot run end-to-end tests because the test environment’s TLS certificate expired, and only the Operations group can renew it.
As Scrum Master, what is the most Scrum-aligned response?
Best answer: A
What this tests: Scrum Master as Servant Leader
Explanation: An impediment is anything that blocks the Scrum Team’s progress toward the Sprint Goal, especially when it requires help outside the team to resolve. The expired TLS certificate prevents end-to-end testing and depends on Operations, so the Scrum Master should make it transparent and work to remove it while the Developers adapt their plan.
In Scrum, an impediment is a problem that reduces the Scrum Team’s progress and that the team cannot readily resolve on its own. The UI work taking longer is normal discovery/uncertainty that the Developers address by re-planning their work in the Sprint Backlog and continuing to collaborate toward the Sprint Goal.
The expired TLS certificate is different: it blocks essential validation for the Sprint Goal and requires action from outside the Scrum Team (Operations). The Scrum Master serves the team by making this impediment visible, helping coordinate with the right people to remove it, and supporting empiricism by enabling timely inspection and adaptation.
A key takeaway is to distinguish “hard blockers outside the team” from “work is harder than expected,” which is managed through re-planning.
The certificate issue blocks progress and is outside the Developers’ control, so the Scrum Master should help remove it while the Developers replan their Sprint Backlog.
Topic: Scrum Master as Servant Leader
Midway through a 2-week Sprint, a stakeholder insists a new multi-factor authentication (MFA) requirement must be included in the Sprint and still delivered by the original Sprint end date for a marketing launch. The Product Owner adds the MFA item to the Sprint Backlog and tells the Developers to “fit it in” without changing the Sprint Goal or discussing trade-offs.
What is the most likely near-term impact?
Best answer: B
What this tests: Scrum Master as Servant Leader
Explanation: Adding work mid-Sprint without renegotiating the Sprint Goal or making trade-offs undermines transparency about what the Sprint is actually trying to achieve. The Developers are pushed toward multitasking and hidden compromises, which makes near-term progress harder to inspect and increases the likelihood of missing the Sprint Goal.
In Scrum, stakeholders can request changes at any time, but the Scrum Team manages those requests through the Product Backlog and by collaborating on trade-offs. When a Product Owner unilaterally pushes additional scope into the Sprint Backlog while keeping the same date and Sprint Goal, the team’s plan becomes unstable and progress toward the Sprint Goal becomes harder to inspect.
Near-term effects typically include:
A better expectation-management approach is to make scope/date trade-offs transparent and renegotiate the Sprint Backlog (and possibly the Sprint Goal) based on what is learned and what remains feasible.
Unnegotiated scope added mid-Sprint increases churn, making progress toward the Sprint Goal harder to inspect and adapt.
Topic: Scrum Master as Servant Leader
Mid-Sprint, a Scrum Master observes the Daily Scrum. Each Developer takes turns giving a status update while looking at the Scrum Master, who asks follow-up questions and then suggests who should pick up which tasks. The Sprint Goal is clear and the team has a visible Sprint Backlog.
What is the best Scrum-aligned correction?
Best answer: A
What this tests: Scrum Master as Servant Leader
Explanation: The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog plan for the next day. When it becomes a reporting session to the Scrum Master, the Scrum Master should coach the team back to self-management and focus on their plan. The Scrum Master can still help remove impediments, but not by directing the work in the event.
This scenario shows the Daily Scrum being used as a status report to the Scrum Master, reinforced by Developers speaking to the Scrum Master and the Scrum Master assigning or steering task selection. In Scrum, the Daily Scrum’s purpose is for the Developers to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.
A Scrum-aligned correction is for the Scrum Master to coach and facilitate so the Developers:
The key shift is restoring Developer ownership of the plan and avoiding command-and-control behavior during the event.
The Daily Scrum is for Developers to inspect progress toward the Sprint Goal and adapt their plan, not to report to the Scrum Master.
Topic: Scrum Master as Servant Leader
In a Scrum Team, a senior stakeholder has been emailing Developers daily with “top priorities” and asking them to add work mid-Sprint. The Product Owner has been accepting these directions and rarely re-orders the Product Backlog.
As Scrum Master, you coach the group to restore clear role boundaries while still using stakeholder input. After the next Sprint, which evidence best validates that role boundaries are improving and the team is delivering value using Scrum?
Best answer: A
What this tests: Scrum Master as Servant Leader
Explanation: The strongest validation is empirical: a Done Increment inspected with stakeholders at the Sprint Review and subsequent adaptation led by the Product Owner. That combination demonstrates real value delivery and that stakeholder input is being funneled through Product Backlog ordering rather than direct mid-Sprint direction to Developers.
In Scrum, stakeholders can provide input and feedback, but the Product Owner is accountable for maximizing value and for ordering the Product Backlog. The clearest indicator that a stakeholder is no longer acting as a de facto Product Owner is not “less noise” or more meetings; it is evidence that the Scrum Team is using Scrum’s inspection and adaptation with the right accountabilities.
A Sprint Review that inspects a Done Increment (meets the Definition of Done) and results in the Product Owner adapting and re-ordering the Product Backlog based on stakeholder feedback shows:
Activity metrics and process outputs can improve without actually restoring who makes Product Backlog decisions.
A Done Increment plus Product Backlog ordering by the Product Owner using stakeholder feedback shows value delivery and restored PO accountability.
Topic: Scrum Master as Servant Leader
Midway through a Sprint, the Scrum Team misses its Daily Scrum forecast twice because:
The Scrum Master wants to optimize near-term predictability without violating Scrum timeboxes or weakening the Definition of Done. What should the Scrum Master do?
Best answer: A
What this tests: Scrum Master as Servant Leader
Explanation: The knowledge gap is a local impediment the Scrum Team can mitigate quickly by swarming and pairing to restore their Sprint forecast. The CI constraint is systemic because it depends on an external policy and requires organizational change, so the Scrum Master should collaborate with IT/leadership to improve it while keeping Sprint timeboxes and the Definition of Done intact.
A local impediment is something the Scrum Team can resolve within its own control (for example, a skill/knowledge gap), so the Scrum Master should facilitate tactics like swarming, pairing, and replanning the Sprint Backlog to improve the Daily Scrum forecast.
A systemic impediment is created by the broader organization (for example, an IT policy that batches CI access weekly). The Scrum Master serves the organization by making the impediment transparent and working with the right people to change the system (agreements, policies, capacity, tooling), rather than trying to “command” a one-off exception. The key is to pursue systemic improvement without changing the Sprint timebox or weakening the Definition of Done to make work appear done.
It addresses the local skill impediment immediately within the Sprint and starts removing the systemic CI constraint through organizational collaboration.
Topic: Scrum Master as Servant Leader
A functional manager tells the Scrum Master they need “proof the team is on track” and asks for a weekly report showing percent complete by person and hours spent. The Scrum Team is working in 2-week Sprints and stakeholders attend the Sprint Review.
Which evidence would best validate progress and value while supporting self-management and meeting the manager’s need for transparency?
Best answer: A
What this tests: Scrum Master as Servant Leader
Explanation: In Scrum, the most reliable evidence of progress and value is a usable Increment that meets the Definition of Done. Inspecting that Done Increment at the Sprint Review, in the context of the Sprint Goal, gives managers transparency through outcomes rather than controlling individuals’ work. This supports self-management while still addressing organizational needs for visibility.
To support self-management, the Scrum Master helps managers focus on outcomes that can be inspected, not on directing how individuals work. The Scrum Guide’s primary measure of progress is the Increment, and the Sprint Review is the event designed to inspect the Increment and adapt based on what was learned.
Outcome-based transparency that meets organizational needs typically includes:
Activity reports and delivery proxies can be useful internally, but they are weaker validation than a Done Increment and can drive command-and-control behavior that undermines self-management.
A Done Increment provides objective, inspectable evidence of value and progress without shifting control to individual activity tracking.
Topic: Scrum Master as Servant Leader
A new Product Owner has been assigned to a Scrum Team. They are struggling to order the Product Backlog and to handle multiple stakeholders who are pushing competing “top priorities.” The team asks what Scrum mechanism best matches the need to support the Product Owner in learning these skills.
What is the best match?
Best answer: D
What this tests: Scrum Master as Servant Leader
Explanation: In Scrum, the Scrum Master serves the Product Owner by coaching them in effective Product Backlog management, including ordering, and by helping improve collaboration with stakeholders. The situation describes a learning and facilitation need, which is a core Scrum Master service to the Product Owner rather than an event or a handoff of accountability.
The core concept is the Scrum Master’s servant-leadership service to the Product Owner. When a new Product Owner struggles with ordering the Product Backlog and navigating competing stakeholder demands, the Scrum Master helps the Product Owner learn and apply techniques for Product Backlog management and helps find ways to collaborate with stakeholders.
That support can include:
Scrum events may provide opportunities to inspect and adapt, but they do not transfer accountability for ordering or replace the need for coaching and stakeholder facilitation.
The Scrum Master is accountable for coaching the Product Owner on effective Product Backlog management and facilitating stakeholder collaboration.
Topic: Scrum Master as Servant Leader
A Scrum Team is in a 2-week Sprint that ends this Friday. The Sprint Goal is “Enable users to reset their password via email.”
On Wednesday, Developers report the feature is coded but integration tests and a required security scan are failing; the Definition of Done requires both to pass. A stakeholder is pressuring the Product Owner to “just extend this Sprint to next Wednesday” so marketing can launch on Monday, and the Product Owner suggests adding a special “go/no-go meeting” after the extended Sprint.
As Scrum Master, what is the BEST next action?
Best answer: B
What this tests: Scrum Master as Servant Leader
Explanation: Scrum relies on a consistent Sprint timebox to create a regular rhythm for inspection and adaptation. Work that does not meet the Definition of Done is not part of the Increment and should not be treated as “almost done” for release decisions. The Scrum Master should reinforce using the existing Scrum events to inspect what is Done and adapt the Product Backlog and plan for the next Sprint.
Extending a Sprint or inserting extra “special” events undermines transparency and the cadence that enables empiricism. With a fixed end date, everyone can inspect a potentially releasable Increment at the Sprint Review and adapt the Product Backlog for what to do next.
In this scenario, the Definition of Done is clear (tests and security scan must pass), so the unfinished work is not part of a Done Increment. The Scrum Master should help the Product Owner and stakeholders understand the trade-off and keep the Sprint timebox intact:
If the Sprint Goal had become obsolete, cancellation is an option, but “just extending” the Sprint or adding new events is not.
Sprints are fixed-length and Scrum uses the existing events to inspect a Done Increment and adapt the Product Backlog for the next 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.