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.

• ✓

  Coach the architecture group and teams toward a shared understanding that architectural guardrails can be expressed as non-functional requirements and definition of done criteria, removing the sequential sign-off gate that blocks self-managing teams.

  Why this is correct

  This is correct because the Scrum Master serves the organization by leading and coaching on Scrum adoption, helping stakeholders see that self-managing teams need technical boundaries rather than approval gates. Expressing architectural expectations as Definition of Done items and non-functional requirements preserves quality while removing the waiting time that breaks Sprint flow, and it builds collaboration between the architecture group and the teams.

• ✗

  Instruct the teams to continue following the sign-off process exactly as defined, since organizational policies always take precedence over Scrum practices and the Scrum Master must not challenge governance.

  Why it's wrong here

  This fails because the Scrum Master's service to the organization includes removing impediments and coaching the enterprise on how Scrum works. Blindly accepting a stage-gate that repeatedly causes missed Sprint Goals leaves the underlying organizational impediment in place. Scrum does not require the Scrum Master to treat every existing policy as immutable; instead, the role includes surfacing and addressing systemic constraints that prevent empiricism and self-management.

• ✗

  Escalate directly to the CEO and request that the architecture group be disbanded, because any centralized technical authority is incompatible with Scrum and must be eliminated for the teams to succeed.

  Why it's wrong here

  This is too extreme and misreads Scrum. Scrum does not forbid technical expertise or centralized standards; it favors self-managing teams working within clear boundaries. Calling for disbanding the architecture group damages relationships and ignores the legitimate need for architectural coherence. A Scrum Master serving the organization would coach toward collaborative, lightweight guardrails rather than pursue removal of an entire function through escalation.

• ✗

  Ask the Product Owner to add a separate backlog item for every architecture approval so the wait time becomes visible in the Sprint Backlog, then let the teams decide whether to keep using the gate.

  Why it's wrong here

  Making the delay visible is useful, but adding approval work as backlog items does not change the policy that causes the delay, and it shifts a systemic organizational issue onto the Product Owner and teams. The Scrum Master serves the organization by addressing the root cause with the architecture group, not by asking teams to absorb a governance bottleneck as ordinary work. Visibility alone rarely removes a mandated approval gate.