Scrum Alliance CSM Certified ScrumMaster Exam Exam Practice Test

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.

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.

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.

Across-functional Scrum Teamis one that has all the skills necessary to deliver ausable Incrementof the product. This ensures that the team is not dependent on external groups to complete their work, enabling them to deliver value independently.

According to the2020 Scrum Guide:

Scrum Teams are cross-functional and self-managing.

Cross-functionality means the team includes all the necessary skills (e.g., development, testing, design) to complete the work in a Sprint and deliver an Increment.

Why the other options are incorrect:

A. Divided into sub-teams:Scrum discourages dividing teams based on function. The team should be collaborative and cross-functional.

B. Distributed:While Scrum Teams can be distributed geographically, this term does not define their ability to deliver a usable Increment.

D. Difficult to manage:A cross-functional Scrum Team is self-managing and does not require external management.

In theScrum framework, the three defined accountabilities are:

Product Owner– Responsible for maximizing the value of the product by managing the Product Backlog.

Scrum Master– Ensures that Scrum is understood and enacted effectively, removes impediments, and serves the Scrum Team and organization.

Developers– Responsible for delivering a "Done" Increment that meets the Sprint Goal.

There is no role forLead Developer,Project Manager, orBusiness Analystin Scrum. Scrum promotes self-management, cross-functional teams, and does not include traditional hierarchical roles.

Why the other options are incorrect:

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

B. Project Manager:Scrum does not include a Project Manager role as tasks and responsibilities are distributed among the Scrum Team.

D. Business Analyst:While the Product Owner may perform some business analysis tasks, there is no separate role for a Business Analyst in Scrum.

When a team member refuses to participate in Sprint Planning, theScrum 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 the2020 Scrum Guide, the Scrum Master is responsible for:

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

Fostering collaborationand 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.

Adone Incrementisusable, meaning it meets the Scrum Team's Definition of Done and can be used or inspected by stakeholders. While the Increment may not always be released to end users, it must be in a usable state to ensure transparency and enable feedback.

According to the2020 Scrum Guide:

An Increment is a concrete step toward the Product Goal.

Each Increment must meet the Definition of Done, ensuring it is usable and provides value, regardless of whether it is immediately released.

Why the other options are incorrect:

A. Prescriptive:Scrum is not prescriptive about how work is done, and "prescriptive" is not a characteristic of a done Increment.

B. Estimable:"Estimable" applies to Product Backlog items but is not a characteristic of a done Increment.

D. Released:While an Increment may be released, it is not a required characteristic. It simply must be in a usable state.

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.

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.

Product Backlog refinementis the act of breaking down and further defining Product Backlog items into smaller, clearer, and more actionable items. This process ensures that the Product Backlog is well-organized, understood, and ready for the upcoming Sprint Planning. Refinement helps the Developers and Product Owner collaborate to add detail, order, and estimates to Product Backlog items.

According to the2020 Scrum Guide:

Product Backlog refinement is an ongoing activity that occurs throughout the Sprint.

It is not a formal event, and its timing and structure are determined by the Scrum Team.

Refinement improves clarity and helps the team better understand upcoming work.

Why the other options are incorrect:

A. a recurring event in the middle of each Sprint:Product Backlog refinement is not a time-boxed event. It occurs continuously, as needed.

C. an opportunity for the Developers to estimate Product Backlog items:While estimation may occur during refinement, the primary purpose is breaking down and clarifying items, not solely estimation.

D. a pre-planning meeting to shorten the length of Sprint Planning:Product Backlog refinement is not a pre-planning meeting but an ongoing activity to prepare for future Sprints.

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.

The primary activity of the Product Owner ismaximizing the value of the Scrum Team's work. This involves managing the Product Backlog, ensuring that the most valuable work is prioritized, and collaborating with stakeholders to define clear goals and objectives for the Scrum Team.

According to the2020 Scrum Guide, the Product Owner:

Ensures that the Scrum Team is working on the most valuable work by continuously prioritizing and refining the Product Backlog.

Collaborates closely with stakeholders to understand their needs and expectations.

Focuses on delivering value while enabling the Scrum Team to achieve their Sprint Goals.

Why the other options are incorrect:

A. Ensuring the Charter is understood:A project charter is not part of the Scrum framework. This option is unrelated to Scrum.

B. Experimenting with Sprint duration:Sprint duration is decided by the Scrum Team and is fixed throughout the Scrum implementation. It is not the Product Owner's responsibility to experiment with this.

D. Managing the Developers:Scrum does not involve "managing" Developers; they are self-organizing and responsible for how they complete their work.

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.

Size(or an estimate) is a required attribute of a Product Backlog item (PBI). PBIs are sized to help the Scrum Team understand the effort required to complete them and to assist in planning and forecasting. TheDevelopersassign the size or estimate during Product Backlog refinement or Sprint Planning.

According to the2020 Scrum Guide, Product Backlog items:

Must be clearly expressed and ordered by priority to maximize value.

Should includeestimates(or sizes) so the Developers can plan the work required to deliver them.

Why the other options are incorrect:

A. Assigned to:PBIs are not assigned to specific individuals. The Developers are self-organizing and collectively decide how to complete the work.

C. Due Date:Scrum does not use due dates for PBIs, as delivery is based on iterative progress and the Sprint Goal.

D. State:While PBIs may be tracked in terms of progress (e.g., "in progress" or "done"), "state" is not a required attribute.

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.