Scrum Alliance CSM Practice Test Questions Answers

TheScrum Mastershouldcoach the Scrum Teamto understand the importance of theSprint Retrospective. This event is essential for inspecting and adapting processes, tools, and team dynamics, enabling continuous improvement in future Sprints.

According to the2020 Scrum Guide:

TheSprint Retrospectiveis a key event where the Scrum Team reflects on their performance and identifies actionable improvements.

It promotes collaboration, accountability, and self-management, all of which are crucial in Scrum.

Why the other options are incorrect:

B. Let the Developers decide:The Sprint Retrospective is a mandatory event for the Scrum Team, and the Developers cannot decide to skip it.

C. Escalate to the Product Owner:The Product Owner is not responsible for team dynamics or facilitating Scrum events. This is the Scrum Master’s responsibility.

D. Exclude those members of the Scrum Team from participating:Excluding team members would undermine team collaboration and the purpose of the event. Instead, the Scrum Master should address the underlying concerns and help the team recognize its value.

The Scrum Team must demonstrateCommitmentto achieve the Sprint Goal. Commitment is one of the five Scrum Values, and it reflects the team’s dedication to the Sprint Goal, the work planned in the Sprint Backlog, and to collaborating effectively. Without commitment, the team cannot focus on delivering the Increment or achieving the Sprint Goal.

According to the2020 Scrum Guide, the Scrum Values are:

Commitment: Dedication to the team’s goals and delivering value.

Focus: Concentrating on the Sprint Goal and avoiding distractions.

Openness: Being transparent about challenges and progress.

Respect: Valuing each team member and their contributions.

Courage: Facing challenges and making tough decisions.

Why the other options are incorrect:

A. Completion:This is not a Scrum Value. Commitment drives completion, but "completion" itself is not a value.

C. Agreement:While agreement is important, Scrum does not define it as a core value.

D. Alignment:While alignment is critical to achieving goals, it is not one of the five Scrum Values.

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.

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.

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.