Free Practice Questions for the Scrum Alliance Scrum Master CSM Exam (2026 Updated)

If a Scrum Team becomes too large, the team should reorganize into multiple cohesive Scrum Teams that share the same Product Goal and Product Backlog . This approach ensures that all teams remain focused on delivering value while maintaining transparency and alignment.

According to the 2020 Scrum Guide :

The ideal size for a Scrum Team is small enough to remain nimble (typically 10 or fewer people).

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 team member refuses to participate in Sprint Planning, the Scrum Master should first meet individually to address their concerns . Understanding the root cause of their reluctance can help the Scrum Master guide them toward recognizing the value of the event. This approach demonstrates respect and a willingness to resolve the issue constructively.

According to the 2020 Scrum Guide , the Scrum Master is responsible for:

Coaching team members on the importance of Scrum events, such as Sprint Planning.

Fostering collaboration and ensuring all team members understand their role and responsibilities in achieving the Sprint Goal.

Why the other options are incorrect:

A. Ask for management's assistance: Involving management should be a last resort. The Scrum Master should first attempt to resolve the issue directly with the team member.

B. Mandate attendance: Forcing participation without addressing the underlying concerns could lead to disengagement and resentment.

C. Discuss the importance of team work: While teamwork is important, addressing the individual's specific concerns first is a more targeted and effective approach.

Facilitating is the activity that seeks to build consensus in a group setting. In Scrum, the Scrum Master often acts as a facilitator , helping the team reach agreements during events such as Sprint Planning, Retrospectives, or backlog refinement sessions. Facilitators guide discussions neutrally, ensuring all voices are heard and helping the group align on decisions.

According to the 2020 Scrum Guide , the Scrum Master:

Facilitates Scrum events as requested or needed.

Removes barriers to communication and fosters collaboration within the team.

Why the other options are incorrect:

A. Coaching: Coaching involves guiding individuals or teams to improve performance, but it is not specifically about building group consensus.

B. Teaching: Teaching focuses on imparting knowledge, not consensus-building.

C. Mentoring: Mentoring involves a one-on-one relationship where the mentor shares knowledge and experience, which is not a group activity.

The Daily Scrum is 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 the 2020 Scrum Guide :

The Developers use the Daily Scrum to inspect progress and adapt their plan to 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.

The Agile principle being practiced when a team focuses on the highest-priority Product Backlog items is "Simplicity - The art of maximizing the amount of work not done is essential." This principle emphasizes delivering only the most valuable work and avoiding unnecessary effort. By working on the most critical items, the team ensures that resources are used efficiently to maximize value.

Why the other options are incorrect:

A. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly: This principle relates to Sprint Retrospectives and improving team processes, not prioritizing backlog items.

C. Business people and developers must work together daily throughout the project: This principle relates to collaboration and communication, not prioritization.

D. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation: This principle emphasizes communication methods, not prioritization.

The Scrum Value most demonstrated when a team completes a task before moving on to the next one is Focus . 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 the 2020 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.

The Scrum Master serves not only the Scrum Team but also the larger organization by ensuring that Scrum is understood and enacted effectively. This aligns with the Scrum Master’s role as a servant leader and a facilitator of organizational agility.

According to the 2020 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.

The Product Owner has the final authority to order the Product Backlog to 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 the 2020 Scrum Guide :

The Product Owner is accountable for managing 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.

Incremental process refers to building and delivering software in small, usable pieces (Increments). In Scrum, each Increment is a usable part of the product that adds value and meets the Definition of Done.

According to the 2020 Scrum Guide :

The Increment is a concrete step toward the Product Goal .

Increments allow for frequent inspection and adaptation while ensuring transparency of progress.

Why the other options are incorrect:

A. An iterative process: While Scrum is iterative, "iterative" describes repeated cycles of planning and improving, whereas "incremental" refers to delivering usable pieces of the product.

C. A lifecycle process: This is a generic term for any process involving software development and does not specifically describe building in pieces.

D. A release process: A release process focuses on deploying software, not the incremental building of usable Increments.

Scrum Artifacts represent work or value, providing transparency and opportunities for inspection and adaptation. The Sprint Backlog is one of the three primary Scrum Artifacts defined in the 2020 Scrum Guide :

Product Backlog : The ordered list of everything that is needed in the product.

Sprint Backlog : The plan for the Sprint, including the Sprint Goal, selected Product Backlog items, and the work plan for delivering the Increment.

Increment : The sum of all work completed during a Sprint that meets the Definition of Done.

Why the other options are incorrect:

A. Definition of Done: While critical to ensuring quality, the Definition of Done is not an Artifact but rather a standard that applies to the Increment.

C. Sprint Goal: The Sprint Goal is part of the Sprint Backlog but is not a standalone Artifact.

D. Sprint Burndown Chart: This is a complementary tool used for tracking progress but is not an official Artifact in Scrum.

Scrum is a lightweight framework designed to help teams and organizations address complex problems and deliver value in an adaptive manner. It is based on the principles of empiricism (transparency, inspection, and adaptation) and is widely used for developing, delivering, and sustaining products in a flexible and iterative way.

According to the 2020 Scrum Guide , Scrum is:

A lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.

Defined by roles, events, artifacts, and rules that are intentionally simple yet highly effective.

Why the other options are incorrect:

A. Kanban: Kanban is a method for visualizing work and improving flow, but it is not a framework specifically designed for solving complex problems like Scrum.

C. Agile: Agile is a broader philosophy or mindset that includes various frameworks (such as Scrum, Kanban, etc.), but Scrum itself is a specific framework.

D. Waterfall: Waterfall is a traditional, sequential approach to project management that lacks the flexibility and adaptiveness of Scrum.

Scrum teams plan work one Sprint at a time , using the Sprint Planning event to adapt the Sprint Backlog based on what was learned in previous Sprints. This approach aligns with Scrum's empirical process control, which relies on inspection and adaptation to plan effectively.

According to the 2020 Scrum Guide :

Sprint Planning creates a Sprint Backlog , which includes the Sprint Goal, selected Product Backlog items, and the plan to deliver them.

Teams adjust their plans Sprint by Sprint, responding to new information, feedback, and changing circumstances.

Why the other options are incorrect:

A. One release at a time, adjusting the number of Sprints to the prior releases’ average velocity: Scrum does not prescribe release-driven planning or adjusting Sprint duration based on velocity.

C. One project at a time, adjusting each Sprint Backlog Item to meet the release date negotiated at inception: Scrum encourages iterative planning within Sprints, not fixed plans tied to predetermined release dates.

D. One Sprint at a time in the Product Backlog Refinement meeting with participation of stakeholders: Product Backlog Refinement is an ongoing activity, not a Sprint planning process. Stakeholders typically participate in Sprint Reviews, not in backlog refinement.