Back to Adopting Scrum in Organizations

Scrum Sprints

5 minutes 5 Questions

A core aspect of adopting Scrum in an organization involves the implementation and understanding of Scrum Sprints. Sprints are time-boxed periods where a set amount of work is completed. Sprints generally last from one week to one month and should remain the same length throughout the entire projec…

Test mode:
Start practice test
CSM - Scrum Sprints Example Questions

Test your knowledge of Scrum Sprints

Question 1

During a Sprint, you observe that one team member constantly interrupts and dismisses the points of other team members in meetings. This is causing tension within the team. As a Scrum Master, how would you handle this situation?

Correct Answer: You set up a one-on-one meeting with the team member to discuss their behavior and its impact on the team dynamics.

The correct approach involves addressing the behavior directly with the individual, providing an opportunity for personal growth and awareness, while indirect methods or general team interventions may not resolve the specific issue. Setting up a one-on-one meeting respects the individual's dignity and underscores the scrum values of respect and courage, inviting them to reflect and adjust their behavior for better team collaboration.

Question 2

During the Sprint, a key stakeholder insists on adding new work because they believe it is 'critical'. As a Scrum Master, how do you handle this situation?

Correct Answer: Collaborate with the Product Owner to assess the value and urgency of the change and decide whether it can wait until the next Sprint or should be considered for the current Sprint backlog with proper adjustments.

In Scrum, the Sprint Backlog is a negotiated set of items that the Development Team commits to complete during a Sprint, which means it's generally fixed and changes are discouraged. However, it recognizes the need for flexibility and adaptation. The correct approach involves balancing respect for the team's current commitment with the ability to adapt to emerging business needs. This necessitates a discussion with the Product Owner, who is responsible for the backlog's prioritization and can negotiate changes with stakeholders. Directly adjusting the current plan without considering the impact on the team or Sprint goals undermines the Scrum values of commitment, focus, and respect. Extending the Sprint or encouraging overtime are not sustainable practices under Scrum principles and fail to respect the team’s work-life balance and the empirical process of inspection and adaptation.

Question 3

At the Sprint Planning meeting, a developer says that some tasks in the Sprint Backlog are not clear to him. What should the ScrumMaster do?

Correct Answer: Encourage the developer to work with the team to clarify the Sprint Backlog items during the Sprint Planning.

In Scrum, the Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. When a developer has concerns about the clarity of tasks in the Sprint Backlog, it is the Scrum Master's role to ensure that the developer collaborates with the team, including the Product Owner if necessary, to clarify these tasks. The correct course of action is to encourage the developer to work with the team to resolve any ambiguities during the Sprint Planning meeting itself, not to delay discussion until the Sprint Retrospective, seek outside help, or have the Scrum Master act as an intermediary.

More Scrum Sprints questions
17 questions (total)
Start 17 question test