CSM Service to the Organization Practice Question
How should a Scrum Master help an organization that is struggling with high levels of 'technical debt' across multiple products?
⚠ Common exam trap
Candidates choose answers where the team secretly fixes technical debt without telling anyone, failing to make the issue transparent to leadership.
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
✓
Facilitate a conversation to make the technical debt transparent and prioritized in the Product Backlog.
The Scrum Master serves the organization by facilitating transparency regarding the impact of technical debt on velocity and quality. By encouraging the Product Owners and leadership to balance feature work with technical refinement, the Scrum Master helps the organization move toward sustainable development. This service is crucial because unchecked debt leads to slower delivery cycles and increased maintenance costs, ultimately hindering the organization's ability to respond to competitive market pressures over time.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Direct the developers to stop all feature work until all technical debt is resolved.
Why it's wrong here
Stopping all feature development is rarely a viable business strategy and ignores the need for incremental value delivery. The Scrum Master should facilitate a balanced approach where technical debt is addressed iteratively alongside new features. Forcing an 'all-or-nothing' approach creates friction with stakeholders and risks stalling the product's market viability completely.
- ✓
Facilitate a conversation to make the technical debt transparent and prioritized in the Product Backlog.
Why this is correct
Making technical debt visible allows the Product Owner to make informed decisions about trade-offs. By including debt reduction in the backlog, the organization treats it as work that provides business value through increased speed and reliability. This professional approach ensures that technical quality is managed continuously rather than ignored until it becomes a crisis.
- ✗
Report the developers' lack of quality to the human resources department.
Why it's wrong here
Technical debt is typically a systemic issue resulting from past organizational decisions, not just individual developer performance. Reporting developers to HR is a punitive measure that ignores the root causes and destroys trust. It is an ineffective strategy that fails to address the underlying process problems and discourages transparency within the team.
- ✗
Advise the organization to ignore technical debt as it is not a direct customer-facing feature.
Why it's wrong here
Ignoring technical debt leads to a 'death spiral' where new development becomes exponentially more expensive. This advice would be irresponsible and harmful to the organization's long-term health. A Scrum Master must promote sustainable development practices, and ignoring systemic quality issues is the opposite of the professional guidance that the organization requires.
About these practice questions
Courseiva writes every CSM question from scratch — 312 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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 Scrum Alliance exam blueprint
This CSM practice question is part of Courseiva's free Scrum Alliance 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 CSM exam.