Scrum Master Accountabilities and Professional Scrum
Serving three directions
The Scrum Master is accountable for the Scrum Team's effectiveness. That shows up as service to the team (coaching self-management and cross-functionality, causing the removal of impediments, ensuring events are positive, productive and kept within timebox), to the Product Owner (helping find techniques for effective goal and backlog management, facilitating stakeholder collaboration), and to the organization (leading, training and coaching Scrum adoption; planning and advising on implementation; removing barriers between stakeholders and teams).
Professional Scrum mindset
The exam rewards a servant-leader, coaching stance. The SM does not command, does not own the backlog, does not assign work, and does not act as a gatekeeper between the team and stakeholders. When something is wrong, the SM makes the problem visible, teaches the why behind the framework, and lets those accountable decide - while still protecting the team's ability to self-manage.
Traps to watch
- Doing instead of coaching - "the SM reorganizes the board" is usually wrong; "the SM helps the team see the problem and choose" is usually right.
- Removing impediments means causing them to be removed, which may include escalation, not personally fixing everything.
- Protecting the Sprint does not mean shielding the team from all feedback; it means protecting the Sprint Goal from unmanaged change.
- Confusing the SM with a project manager, tech lead, or HR function.
Rule of thumb
For any scenario, ask: "Does this action increase the team's ability to solve the problem itself?" If yes, it is likely the intended answer. If it solves it for them and removes their ownership, it usually is not.
Worked example
A team keeps overcommitting. Weak answer: the SM caps the Sprint Backlog. Strong answer: the SM facilitates the Retrospective so the team examines why, and coaches them on using the Sprint Goal and past data to forecast - the team owns the fix.