CSM Certified Scrum Master Free Practice Test — 30 Questions

The practice bank consistently emphasizes that the Scrum Master is a servant-leader who facilitates, coaches, and removes impediments—but does not manage the team or order their work. Many scenarios test your ability to distinguish between actions that foster self-management (e.g., facilitating discussions) versus directive actions (e.g., assigning tasks or making decisions for the team). The correct answers almost always involve guiding the team to solve problems collaboratively, using events like the Retrospective or a dedicated meeting. The Scrum Master's primary accountability is ensuring the Scrum framework is understood and enacted, not performing the work of the Development Team or the Product Owner.

A recurring theme is the Scrum Master's role in fostering a self-managing Development Team. When a team struggles with task allocation, collaboration, or meeting Sprint Goals, the best action is to facilitate a Retrospective or a discussion where the team identifies root causes and devises its own improvements. The practice bank warns against solutions where the Scrum Master assigns tasks, imposes processes, or directly addresses an individual's performance without involving the team. Self-management is upheld when the team collectively owns its methods, commitments, and even its interpersonal challenges. The Scrum Master's tools are coaching questions, process guidance, and a safe environment for open dialogue.

The practice bank is rich with scenarios where external dependencies, stakeholder demands, or organizational constraints threaten the team's progress. The Scrum Master's effective response is to facilitate communication between the affected parties (team, Product Owner, external teams, management) to negotiate solutions, not to personally fix the technical problem or shield the team completely. When the Product Owner overrides estimates or introduces mid-Sprint changes, the Scrum Master must coach them on the impact of these actions and facilitate a discussion to reestablish respect for the Sprint Goal. Similarly, when external teams or senior executives bypass Scrum roles, the Scrum Master should reinforce the process by involving the Product Owner and facilitating a conversation.

The underlying lesson across many questions is that the Scrum Master must protect Scrum values—commitment, courage, focus, openness, and respect—and the empirical pillars of transparency, inspection, and adaptation. For example, when a stakeholder bypasses the Product Owner, the Scrum Master must courageously address the disruption while respecting the stakeholder's intent. When a team member struggles, the Scrum Master fosters openness by facilitating a team discussion rather than gossiping or directly confronting the individual. The practice bank also tests your understanding of the Sprint Review's purpose: it is for inspecting the Increment and adapting the Product Backlog, not for making mid-Sprint changes. Keeping the Sprint Goal stable is a core principle.