Free Scrum Alliance CSM Practice Exam with Questions & Answers

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.

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.

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

According to the2020 Scrum Guide:

Sprint Planning creates aSprint 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.

TheDevelopersare the ones responsible for executing the work contained in the Sprint Backlog. The Sprint Backlog is created during Sprint Planning and consists of:

TheSprint Goal(why the Sprint exists).

Selected Product Backlog items(what needs to be done).

Aplanfor delivering the increment (how the work will be achieved).

Per the2020 Scrum Guide, only Developers can deliver a Done Increment at the end of the Sprint. The Developers are accountable for:

Creating a plan for the Sprint Goaland Sprint Backlog.

Executing the workto meet the Definition of Done and the Sprint Goal.

Adapting their plandaily based on progress and challenges.

Why the other options are incorrect:

A. Scrum Master:The Scrum Master facilitates the process and removes impediments but does not perform the work.

B. Scrum Team:While the Scrum Team collectively owns the Sprint Goal, only the Developers execute the actual work to meet it.

D. Product Owner:The Product Owner prioritizes the Product Backlog and ensures value delivery but does not execute the work in the Sprint 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.

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.

TheSprint Backlogis owned solely by theDevelopers, as they are responsible for planning, managing, and executing the work required to meet the Sprint Goal. The Sprint Backlog is ahighly visible, real-time planfor delivering the Increment. It includes:

TheSprint Goal.

The set of Product Backlog items selected for the Sprint.

A plan for delivering the Increment.

According to the2020 Scrum Guide, the Developers:

Have full ownership and accountability over the Sprint Backlog.

Decide how to adapt their work plan daily to achieve the Sprint Goal.

Why the other options are incorrect:

A. Scrum Master:The Scrum Master facilitates the Scrum process but does not own the Sprint Backlog.

C. Product Owner:The Product Owner manages the Product Backlog, not the Sprint Backlog.

D. Scrum Team:While the Sprint Goal is owned by the entire Scrum Team, the Sprint Backlog is specifically managed and executed by the Developers.

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.

TheScrum Masterworks with theScrum Teamand other involved parties (such as stakeholders) to ensure that artifacts aretransparent. Transparency is one of the three pillars of empiricism in Scrum and is critical for effective inspection and adaptation. If artifacts (e.g., Product Backlog, Sprint Backlog, Increment) are not transparent, it can hinder decision-making and progress.

According to the2020 Scrum Guide, the Scrum Master is responsible for ensuring that everyone involved understands:

The purpose of the artifacts(e.g., Product Backlog, Sprint Backlog, Increment).

The Definition of Done, to ensure shared understanding of what constitutes a completed work item.

Why the other options are incorrect:

A. End users:While feedback from end users is important, they are not directly responsible for ensuring transparency of artifacts.

C. Management team:Management is not directly involved in artifact transparency, as this is primarily a collaboration between the Scrum Team and relevant stakeholders.

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

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.