CSM Scrum Alliance Certified ScrumMaster Exam Free Practice Exam Questions (2025 Updated)

The Scrum Team must demonstrateCommitmentto achieve the Sprint Goal. Commitment is one of the five Scrum Values, and it reflects the team’s dedication to the Sprint Goal, the work planned in the Sprint Backlog, and to collaborating effectively. Without commitment, the team cannot focus on delivering the Increment or achieving the Sprint Goal.

According to the2020 Scrum Guide, the Scrum Values are:

Commitment: Dedication to the team’s goals and delivering value.

Focus: Concentrating on the Sprint Goal and avoiding distractions.

Openness: Being transparent about challenges and progress.

Respect: Valuing each team member and their contributions.

Courage: Facing challenges and making tough decisions.

Why the other options are incorrect:

A. Completion:This is not a Scrum Value. Commitment drives completion, but "completion" itself is not a value.

C. Agreement:While agreement is important, Scrum does not define it as a core value.

D. Alignment:While alignment is critical to achieving goals, it is not one of the five Scrum Values.

The described scenario aligns with"Individuals and Interactions over Processes and Tools", one of the four core Agile Values from the Agile Manifesto. This value emphasizes the importance of collaboration, communication, and teamwork over reliance on rigid processes or tools. Scrum encourages team members to work together closely to solve problems and deliver high-quality software.

Why the other options are incorrect:

A. Individuals and Interactions over Working Software:While this value mentions "Working Software," the scenario focuses on collaboration among team members, which relates more to prioritizing individuals and interactions.

C. Individuals and Interactions over Contract Negotiation:This value applies to collaboration with stakeholders and customers rather than collaboration within the team.

D. Individuals and Interactions over Customer Collaboration:While customer collaboration is essential, the scenario specifically highlights collaboration among team members.

TheDaily Scrumis a time-boxed event that allows theDevelopersto inspect progress toward the Sprint Goal and adapt their plan as necessary. This daily inspection and adaptation ensure the team stays aligned and on track to meet their objectives.

According to the2020 Scrum Guide:

The Developers inspect how progress is trending toward completing the work in the Sprint Backlog.

They adapt their work plan based on challenges, progress, or new information.

Why the other options are incorrect:

B. Assign tasks:Tasks are not assigned in Scrum. Developers are self-organizing and decide collaboratively how to accomplish their work.

C. Demo the changes to Stakeholders:Demos occur during the Sprint Review, not the Daily Scrum.

D. Estimate the pending work:While work may be discussed, the Daily Scrum is not used for estimation purposes.

If a Scrum Team becomes too large, the team shouldreorganize into multiple cohesive Scrum Teamsthat share the sameProduct GoalandProduct Backlog. This approach ensures that all teams remain focused on delivering value while maintaining transparency and alignment.

According to the2020 Scrum Guide:

Theideal sizefor a Scrum Team is small enough to remain nimble (typically 10 or fewerpeople).

When a Scrum Team becomes too large, it should form multiple smaller teams, all working from the same Product Backlog and pursuing the same Product Goal.

Why the other options are incorrect:

A. Split into sub-teams based on function:Scrum encourages cross-functional teams, so dividing based on function contradicts Scrum principles.

C. Divide into separate teams each with their own Product Owner:A single Product Owner should manage the Product Backlog to ensure alignment and avoid conflicting priorities.

D. Do nothing and focus on delivering a usable product Increment:Not addressing the issue of an oversized team can lead to inefficiencies and reduced team effectiveness.

When a Scrum Master encounters resistance from outside the Scrum Team, their role is to act as aservant leader and coach, ensuring the organization's adoption of Scrum is effective. Resistance often stems from a lack of understanding or buy-in regarding the value of Scrum.

According to the2020 Scrum Guide, the Scrum Master serves the organization in several ways, including:

Leading, training, and coaching the organization in its Scrum adoption.

Planning and advising Scrum implementations within the organization.

Helping employees and stakeholders understand and enact an empirical approach for complex work.

In this case, the Scrum Master collaborates with other Scrum Masters to amplify the effectiveness of Scrum across the organization. This collaboration is essential for addressing systemic challenges or resistance to Scrum.

Why the other options are incorrect:

A. Escalate to management to reprimand the resisters:Escalating and seeking reprimand is not aligned with the Scrum Master's role as a facilitator and coach. This approach could create conflict rather than resolve resistance.

B. Not intervene in the business of others:The Scrum Master’s role involves actively addressing impediments and resistance. Avoiding intervention undermines their responsibility to promote Scrum.

C. Create a status update meeting for all Scrum Masters to coordinate teamdependencies:While collaboration among Scrum Masters is essential, "status update meetings" are not a Scrum practice, and coordination of dependencies is typically handled within Sprint Planning or during collaborative refinement sessions.

The Product Owner is accountable forcreating and ordering Product Backlog itemsto maximize the value of the product. This includes clearly expressing Product Backlog items, ordering them to maximize value, and ensuring that the Product Backlog is transparent and understood.

According to the2020 Scrum Guide, the Product Owner is accountable for:

Maximizing the value of the product resulting from the work of the Scrum Team.

Effectively managing the Product Backlog by ensuring it is prioritized and transparent.

Creating Product Backlog items in collaboration with stakeholders and the Scrum Team.

Why the other options are incorrect:

A. Describe the solution:The Product Owner defines the "what" (desired outcomes), not the technical "solution," which is determined by the Developers.

B. Manage the Developers:The Product Owner does not manage the Developers. Developers are self-managing and self-organizing.

D. Recognize titles:Titles have no significance in Scrum, and this is not a responsibility of any Scrum role.

DuringSprint Planning, the Scrum Team plans the work to be performed in the upcoming Sprint. The event is time-boxed and is attended by the entire Scrum Team. The main outcomes of Sprint Planning are:

A Sprint Goalthat defines the purpose of the Sprint.

Selected Product Backlog itemsthat are forecasted to be delivered during the Sprint.

A plan for how the work will be completed, which is created by the Developers.

Why the other options are incorrect:

B. Demo of the previous increment is done:Demonstrations and feedback occur during the Sprint Review, not Sprint Planning.

C. Customers will share the feedback:Feedback from customers is gathered during the Sprint Review, not Sprint Planning.

D. The Product Backlog is refined:Product Backlog refinement is an ongoing activity, not a specific focus of Sprint Planning.

TheProduct Ownerhas the final authority toorder the Product Backlogto maximize value. They are responsible for ensuring that the most valuable and important work is prioritized so that the Scrum Team delivers maximum value in each Sprint.

According to the2020 Scrum Guide:

The Product Owner is accountable formanaging the Product Backlog, which includes ordering items to best achieve the Product Goal.

While the Developers may provide input, the final decision on ordering lies with the Product Owner.

Why the other options are incorrect:

A. Lead Developer:Scrum does not have a "Lead Developer" role or accountability.

B. Scrum Master:The Scrum Master facilitates and coaches but does not manage or order the Product Backlog.

D. Developers:While Developers provide input during refinement and Sprint Planning, they do not have the authority to order the Product Backlog.

One of the key services aScrum Master provides to the Product Owneris helping them findeffective Product Backlog management techniques. This ensures that the Product Owner can maximize the value of the product and effectively manage the Product Backlog.

According to the2020 Scrum Guide, the Scrum Master serves the Product Owner by:

Helping the Product Owner find techniques for effective Product Goal definition and Product Backlog management.

Facilitating stakeholder collaboration when needed.

Supporting empirical product planning for complex environments.

Why the other options are incorrect:

A. Assign tasks to the Developers:Tasks are not assigned in Scrum. Developers are self-organizing and responsible for determining how they will complete the work.

B. Write user stories:Writing user stories is a Product Owner responsibility, not the Scrum Master's.

C. Prioritize the backlog:The Product Owner prioritizes the Product Backlog, not the Scrum Master.

Product Backlog management is primarily the responsibility of theProduct Owner. One of their key activities is toclearly express Product Backlog items, ensuring they are transparent and understandable for the Developers. This helps the Scrum Team deliver valuable Increments.

According to the2020 Scrum Guide, Product Backlog management includes:

Clearly expressing Product Backlog items.

Ordering the items to maximize value.

Ensuring the Product Backlog is transparent, visible, and understood.

Why the other options are incorrect:

B. Creating Sprint tasks:Sprint tasks are part of the Developers’ detailed planning during the Sprint and are not part of Product Backlog management.

C. Facilitating the Daily Scrum:This is a responsibility of the Developers, and the Scrum Master may only facilitate if explicitly requested.

D. Planning the Sprint Backlog:The Sprint Backlog is planned during Sprint Planning and is primarily the Developers' responsibility, not part of Product Backlog management.

TheScrum Valuemost demonstrated when a team completes a task before moving on to the next one isFocus. In Scrum, the team is expected to focus on the work required to meet the Sprint Goal. Completing one task at a time shows that the team prioritizes their attention and energy on delivering work of high quality, avoiding multitasking and distractions.

According to the2020 Scrum Guide, focus is one of the five Scrum Values, which include:

Commitment: Dedication to the goals of the team and the Sprint.

Focus: Concentrating on the work at hand to ensure maximum productivity and value.

Respect: Valuing each team member and their contributions.

Courage: Facing challenges and delivering value despite uncertainties.

Openness: Transparency in communication and progress.

Why the other options are incorrect:

A. Commitment:While commitment is important, the act of completing a task before moving to the next one primarily demonstrates focus rather than commitment to goals.

C. Respect:Respect refers to valuing team members and their contributions, not the practice of completing one task at a time.

D. Courage:Courage involves tackling difficult challenges or speaking up, but it is not directly related to task completion.

TheDaily Scrumis the event where impediments to achieving the Sprint Goal are shared. It is a time-boxed event (15 minutes) held every day during the Sprint. During this event, the Developers inspect their progress toward the Sprint Goal and identify any blockers or impediments that need to be addressed.

According to the2020 Scrum Guide:

The Developers use the Daily Scrum to inspect progress andadapt their planto achieve the Sprint Goal.

Impediments are raised and addressed by the Scrum Master if they cannot be resolved by the team.

Why the other options are incorrect:

B. Sprint Planning:Sprint Planning is focused on creating the Sprint Goal and selecting Product Backlog items for the Sprint, not sharing impediments.

C. Sprint Retrospective:The Retrospective focuses on process improvements and team dynamics, not day-to-day impediments during the Sprint.

D. Sprint Review:The Sprint Review is about presenting the Increment and gathering feedback, not resolving impediments.

When Developers ask for help or admit they do not know something, they demonstrateCourage, one of the five Scrum Values. It takes courage to be open about challenges or limitations and seek assistance, as it fosters collaboration, transparency, and trust within the team.

According to the2020 Scrum Guide, the Scrum Values include:

Commitment: Dedicated to the team’s goals and delivering value.

Focus: Concentrating on the Sprint Goal and avoiding distractions.

Openness: Transparent about work and progress.

Respect: Valuing each other's contributions and perspectives.

Courage: Taking risks, speaking up, and tackling challenges.

Why the other options are incorrect:

A. Respect:Respect is about valuing team members' contributions, but asking for help reflects personal courage.

C. Commitment:Commitment relates to dedication to achieving goals, not specifically asking for help.

D. Focus:Focus involves prioritizing and working toward the Sprint Goal, not addressing knowledge gaps or challenges.

The Scrum Master serves not only theScrum Teambut also thelarger organizationby ensuring that Scrum is understood and enacted effectively. This aligns with the Scrum Master’s role as aservant leaderand a facilitator of organizational agility.

According to the2020 Scrum Guide, the Scrum Master serves:

The Scrum Team: By coaching team members, removing impediments, and ensuring Scrum events are productive and timeboxed.

The Product Owner: By helping with effective Product Backlog management and stakeholder collaboration.

The Organization: By leading Scrum adoption, coaching employees and stakeholders, and removing systemic barriers.

Why the other options are incorrect:

A. The Scrum Team only:While serving the Scrum Team is a key part of the Scrum Master’s role, they also serve the organization and the Product Owner.

B. The management:The Scrum Master works with management but does not exclusively serve them. Their focus is on enabling Scrum practices across the organization.

C. No one:This is incorrect as the Scrum Master’s role is fundamentally about serving and supporting others.