CSM Service to the Organization Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Record the manual regression time as an impediment in the Sprint Retrospective and continue with the current vendor until the contract expires, because procurement decisions are outside the Scrum Master's scope and cannot be influenced.

  Why it's wrong here

  Logging the impediment without acting leaves the organization unaware of a systemic constraint that undermines every team using the contract. The claim that procurement cannot be influenced is false; the Scrum Master serves the organization by coaching across departments. Waiting years for a contract to expire allows the Definition of Done to keep eroding and normalizes lower quality, which is contrary to the role's purpose.

• ✗

  Advise the teams to reduce the scope of their Definition of Done so that manual regression testing no longer blocks a Product Increment, allowing them to meet Sprint Goals with the current tooling.

  Why it's wrong here

  Lowering the Definition of Done to fit a tooling constraint hides the problem and degrades quality. The Scrum Master serves the organization by addressing the impediment, not by weakening the quality standard. Reducing the Definition of Done may make Sprints appear successful, but it increases technical risk and contradicts the empirical transparency Scrum depends on. The procurement constraint is the real issue and should be raised with the people who can change it.

• ✓

  Work with the procurement department and teams to make the testing-tool limitation and its impact on delivery visible, and coach them on options such as adding automation-capable tooling or amending the vendor agreement to support the Definition of Done.

  Why this is correct

  This is correct because serving the organization means helping it understand how procurement decisions affect the teams' ability to deliver a Done Increment. By making the impact visible and coaching procurement and teams together, the Scrum Master enables a systemic fix rather than a workaround. This respects the organization's contracting reality while advocating for the technical capability the Definition of Done requires.

• ✗

  Direct the developers to build a custom automation framework from scratch during Sprint time, since the Scrum Master is responsible for removing impediments and can assign technical work when tooling is inadequate.

  Why it's wrong here

  The Scrum Master does not assign technical work or dictate engineering solutions; that authority belongs to the self-managing developers. Ordering a from-scratch framework also ignores the procurement constraint that caused the problem and may create unsustainable maintenance work. While removing impediments is part of the role, it is done by coaching and facilitating organizational change, not by directing the team's technical choices.