Scrum Alliance CSM Certified ScrumMaster Exam Exam Practice Test

Fromself-organizing teams,the best architecture, requirements, and designsemerge. This aligns with one of theAgile Manifesto Principles, which states:

"The best architectures, requirements, and designs emerge from self-organizing teams."

Self-organizing teams have the autonomy to make decisions, collaborate effectively, and adapt their processes to deliver high-quality solutions.

Self-organizing teams work without being micromanaged, leveraging their expertise and collective intelligence to solve complex problems and create innovative solutions.

Why the other options are incorrect:

A. The best process flows, user stories and requirements:While self-organizing teams improve processes, the Agile principle specifically mentions architecture, requirements, and designs.

C. The best designs, user stories and Sprint Backlog:The Sprint Backlog is an artifact, not an outcome of self-organization.

D. The best architecture, user stories and requirements:User stories are part of backlog items, but the principle focuses on architecture, requirements, and designs.

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.

Thetypical size of an effective Scrum Team is ten or fewer people, as stated in the2020 Scrum Guide. This includes the Product Owner, Scrum Master, and Developers. Smaller teams ensure better communication, collaboration, and effectiveness, as larger teams can introduce inefficiencies and coordination challenges.

Why the other options are incorrect:

B. Size doesn't matter as long as the Scrum Master coordinates the work in collaboration with the Product Owner:Scrum Teams are self-managing and self-organizing; they do not rely on the Scrum Master to coordinate work. Team size does matter for effectiveness.

C. Bigger teams communicate better, are more productive and produce better results:Larger teams often face communication and coordination challenges, reducing productivity and effectiveness.

D. When a team expands beyond ten, activities, like verification and operations, are assigned to a different team:Scrum encourages cross-functional teams that handle all activities required to deliver a usable Increment without assigning work to other teams.

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.

TheScrum Masteris accountable for ensuring Scrum is understood and enacted. They are responsible for coaching the Scrum Team and the organization in adopting Scrum practices and principles. The Scrum Master acts as a servant leader, guiding the team and stakeholders in understanding and applying Scrum effectively to deliver value.

According to the2020 Scrum Guide, the Scrum Master is accountable for:

Establishing Scrum as defined in the Scrum Guide.

Helping everyone understand Scrum theory and practice.

Removing impediments and fostering an environment where Scrum can thrive.

Why the other options are incorrect:

A. Developers:Developers are accountable for creating the Increment but not for ensuring Scrum is understood across the organization.

B. Product Owner:The Product Owner is responsible for managing the Product Backlog and ensuring value delivery, not for ensuring Scrum adoption.

D. Project Sponsor:There is no role of "Project Sponsor" in Scrum.

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.

One of the key accountabilities of aScrum Masteris toimprove the Scrum Team's effectiveness. This aligns with the Scrum Master's role as a servant leader who helps the team deliver value through better practices, collaboration, and adherence to Scrum principles.

According to the2020 Scrum Guide, the Scrum Master is accountable for:

Establishing Scrum as defined in the Scrum Guide, helping everyone understand its theory and practices.

Improving the Scrum Team's effectivenessby enabling the team to self-manage, improve cross-functionality, and focus on delivering high-value Increments.

Removing impedimentsthat hinder progress and supporting the team in achieving its Sprint Goals.

Why the other options are incorrect:

A. Set the budget:The Scrum Master does not manage budgets. Budgeting decisions are outside the scope of the Scrum framework.

B. Provide estimates:Developers are responsible for providing estimates during Product Backlog refinement and Sprint Planning.

D. Decide when to release the product:Decisions about releases are made collaboratively by theProduct Owner, often based on business needs and stakeholder input.

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.

ScrumArtifactsrepresent work or value, providing transparency and opportunities for inspection and adaptation. TheSprint Backlogis one of the three primary Scrum Artifacts defined in the2020 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.

Thethree Scrum artifacts—Product Backlog,Sprint Backlog, andIncrement—providetransparencyinto the work and enable opportunities forinspection and adaptation. These artifacts are essential to ensuring the Scrum Team and stakeholders can inspect progress and adapt plans to maximize value.

According to the2020 Scrum Guide:

Product Backlog: Represents all the work needed to achieve the Product Goal and allows inspection and prioritization of upcoming work.

Sprint Backlog: A real-time plan for the Sprint that provides transparency into what the team is working on and allows inspection and adaptation during the Sprint.

Increment: The outcome of the Sprint that is usable and meets the Definition of Done, enabling stakeholders to inspect progress and provide feedback.

Why the other options are incorrect:

A. Burndown Charts, release plan and Product Backlog:Burndown charts and release plans are complementary tools, but they are not official Scrum artifacts.

C. Definition of Done and Product Backlog:The Definition of Done is not an artifact but a shared understanding of when work is complete.

D. Definition of Done, Sprint Backlog and Product Backlog:While the Sprint Backlog and Product Backlog are artifacts, the Definition of Done is not.

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.

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.

TheProduct Owneris accountable for ordering theProduct Backlog. This responsibility includes prioritizing items to maximize the value of the product and ensuring that the most important work is addressed first.

According to the2020 Scrum Guide:

The Product Owner is responsible formanaging the Product Backlog, which includesorderingthe Product Backlog items to achieve the Product Goal effectively.

The Product Owner works collaboratively with stakeholders, the Scrum Team, and other involved parties to understand priorities, but the final decision on ordering rests solely with them.

Why the other options are incorrect:

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

B. Stakeholders:Stakeholders provide input and feedback, but they do not have the authority to order the Product Backlog.

D. Developers:Developers collaborate with the Product Owner to clarify and refine items but do not make decisions about ordering the backlog.

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.

TheSprint Reviewis heldonce at the end of every Sprint. It is a time-boxed event where the Scrum Team and stakeholders collaborate to inspect the Increment, review progress toward the Product Goal, and adapt the Product Backlog as needed.

According to the2020 Scrum Guide:

The purpose of the Sprint Review is to discuss what was completed during the Sprint and what could be done next to optimize value delivery.

It occursonce at the end of every Sprint, ensuring transparency and stakeholder involvement.

Why the other options are incorrect:

B. One in the middle and one at the end of every Sprint:The Sprint Review is not conducted multiple times within a Sprint.

C. Once at the beginning of the Sprint:The Sprint Review is held at the end of the Sprint, not the beginning.

D. Daily:The Sprint Review is not a daily event. TheDaily Scrumoccurs daily.