Certified Scrum Master (CSM) Practice Exam

The Certified ScrumMaster (CSM) is a globally recognized certification awarded by Scrum Alliance to professionals who have completed a ScrumMaster training course and demonstrated understanding of the Scrum framework. Scrum is an agile methodology used in project management, particularly in software development, to deliver high-quality products through iterative cycles called sprints. The ScrumMaster serves as a facilitator, ensuring that the team adheres to Scrum practices, removes obstacles, and fosters a collaborative environment.

Achieving the CSM certification signifies a commitment to continuous improvement and leadership within agile teams. It equips professionals with the skills to guide teams through the Scrum process, enhance productivity, and deliver value to stakeholders. This certification is ideal for individuals aiming to play a pivotal role in agile project management and team facilitation.

Who should take the Exam?

This exam is ideal for:

• Project Managers
• Team Leads
• Business Analysts
• Software Developers
• Quality Assurance Professionals
• Product Owners
• Individuals New to Agile

Skills Required

• Understanding of Agile Principles
• Facilitation Skills
• Conflict Resolution
• Communication
• Problem-Solving
• Coaching
• Time Management

Knowledge Gained

• Scrum Framework
• Agile Practices
• Team Dynamics
• Stakeholder Engagement
• Impediment Removal
• Sprint Planning
• Product Backlog Management
• Quality Assurance
• Continuous Improvement
• Adaptability

Course Outline

The Certified Scrum Master (CSM) Exam covers the following topics -

Domain 1 - Scrum

• 1.1 describe the responsibilities and accountabilities of the scrum team.
• 1.2 describe the responsibilities and accountabilities of the scrum master.
• 1.3 describe the responsibilities and accountabilities of the developers.
• 1.4 describe the responsibilities and accountabilities of the product owner.
• 1.5 discuss at least two reasons why the product owner is a single person and neither a group nor a committee.
• 1.6 discuss how and why the product owner maintains authority over the product backlog while working collaboratively with developers and stakeholders.
• 1.7 identify at least one example of how a scrum team could inspect and adapt to increase transparency at each of the scrum events.
• 1.8 perform a sprint planning.
• 1.9 perform a sprint review.
• 1.10 perform a sprint retrospective.
• 1.11 describe at least three possible effects of skipping the sprint retrospective.
• 1.12 explain how developers conduct a daily scrum.
• 1.13 discuss at least three ways the daily scrum differs from a status meeting and why the various constraints exist to support the developers.
• 1.14 explain under what conditions a sprint could be terminated prematurely.
• 1.15 explain at least three advantages of a strong definition of done.
• 1.16 outline at least one way to create a definition of done.

Domain 2 - Scrum Master Core Competencies

• 2.1 describe at least three situations in which the scrum master could serve the needs of the scrum team or organization through facilitation.
• 2.2 demonstrate at least three techniques for facilitating group decision making.
• 2.3 discuss how facilitating, teaching, mentoring, and coaching are different.

Domain 3 - Service to the Scrum Team, Product Owner, and Organization

• 3.1 describe three scenarios where the scrum master acts as a leader for the scrum team.
• 3.2 explain the impact of accumulating technical debt.
• 3.3 list at least three development practices that could help their scrum team deliver a high-quality increment and reduce technical debt each sprint.
• 3.4 explain at least three ways the scrum master could support the product owner.
• 3.5 describe at least three organizational impediments that can affect scrum teams.
• 3.6 discuss at least two ways that the scrum master assists the scrum team with impediments.
• 3.7 apply at least one technique that could help resolve an impediment.
• 3.8 summarize at least one organizational design change caused by adopting scrum.
• 3.9 discuss why scrum does not have a project manager.