CSM Sample Questions Answers

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.

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.

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.

TheSprint Retrospectiveis a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. This event focuses oncontinuous improvementby reviewing processes, collaboration, tools, and their adherence to the Definition of Done.

According to the2020 Scrum Guide, the Sprint Retrospective serves the following purposes:

Toinspecthow the last Sprint went in terms of individuals, interactions, processes, tools, and the Definition of Done.

To identify andagree upon actionable improvementsthat will increase the team's effectiveness in future Sprints.

Why the other options are incorrect:

B. Plan the incomplete work for the next Sprint and submit reasons to the Product Owner:This is not the purpose of the Sprint Retrospective. Sprint Planning is the event where the team plans the upcoming Sprint.

C. Explain what Backlog items have been done and what has not been done:This describes the Sprint Review, where the team discusses completed and incomplete Product Backlog Items with stakeholders.

D. Identify Developers who did not perform well in the Sprint:Scrum encourages collaboration, respect, and continuous improvement, not blaming individuals for shortcomings.

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.

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.

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.

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.

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.

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.

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.

TheScrum Masteris responsible for leading and coaching the organization in its Scrum adoption. They play a critical role in helping the organization understand and implement Scrum practices, fostering an environment of empiricism and continuous improvement.

According to the2020 Scrum Guide, the Scrum Master serves the organization by:

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

Helping employees and stakeholders understand and enact an empirical approach to work.

Removing barriers between stakeholders and Scrum Teams.

Why the other options are incorrect:

A. Customer:Customers provide requirements and feedback but do not lead or coach the organization in Scrum adoption.

B. Product Owner:The Product Owner manages the Product Backlog and focuses on delivering value but is not responsible for organizational Scrum adoption.

C. Developers:Developers are responsible for delivering the Increment and are not accountable for coaching the organization.