Scrum Retrospectives test - Professional Scrum Master I questions

Question 1

Your Scrum team identifies a new user story during the sprint. What should be the team's approach to inspect and adapt?

Set aside time during the sprint review to present the new user story to stakeholders for their input on its priority and scope, potentially delaying the current sprint's review. Collaborate with the Product Owner to evaluate the new user story for potential inclusion in a future sprint backlog. Automatically add the new user story to the current sprint, increasing the sprint goal to accommodate the additional work. Immediately reprioritize the sprint backlog to accommodate the new user story, regardless of the impact on current sprint commitments.

Correct Answer: Collaborate with the Product Owner to evaluate the new user story for potential inclusion in a future sprint backlog.

The correct approach when a new user story is identified during a sprint is to collaborate with the Product Owner to assess its importance and decide if it should be added to the product backlog for consideration in future sprints. It's not appropriate to unilaterally add it to the current or future sprints without discussion, nor should the team reprioritize ongoing work without consulting the Product Owner. Discussing the new user story during the sprint review is not the right forum as the sprint review is meant for inspecting the increment and adapting the product backlog if needed, not for backlog refinement activities.

Question 2

During retrospectives, one of your team members, Bob, consistently blames others for the failures. What should you, as a Scrum Master, do to maintain Psychological Safety?

Introduce a rule in the retrospective that prohibits pointing fingers at individuals to ensure a more generalized discussion of issues. Organize a dedicated session to teach the team about conflict resolution strategies, emphasizing the importance of empathy and listening in resolving team conflicts. This session would not directly address Bob's behavior but aims to improve overall team interaction. Allocate specific time during retrospectives for each team member to express grievances, ensuring everyone gets a moment to speak, including criticisms. Discuss with Bob privately about the impact of his behavior on team dynamics and encourage him to share feedback in a more constructive manner.

Correct Answer: Discuss with Bob privately about the impact of his behavior on team dynamics and encourage him to share feedback in a more constructive manner.

The correct answer involves directly addressing the disruptive behavior in a private and constructive manner, which helps maintain psychological safety. The first wrong answer attempts to indirectly solve the problem through rule implementation, which may suppress open dialogue rather than encourage constructive feedback. The second wrong answer might escalate the issue by giving it a formal platform, potentially worsening the psychological safety. The third wrong answer, while potentially beneficial for long-term team development, does not directly address the immediate issue with Bob's behavior in retrospectives.

Question 3

In the Sprint Retrospective, one team member, Alex, raises a highly critical feedback concerning the entire team's performance. The team seems visibly offended and defensive. As a Scrum Master, how would you ensure psychological safety in this scenario?

Suggest that the team votes on whether Alex's feedback is valid or not, and proceed based on the majority decision. Encourage team members to focus on specifics of the feedback rather than taking it personally, and brainstorm actionable steps for improvement. Redirect the conversation to highlight the team's achievements in the past sprints, avoiding addressing the critical feedback directly. Advocate for developing a new set of team agreements to prevent such critical feedback in future retrospectives, focusing on communication guidelines without addressing the current issue.

Correct Answer: Encourage team members to focus on specifics of the feedback rather than taking it personally, and brainstorm actionable steps for improvement.

The correct approach emphasizes the importance of addressing feedback constructively, ensuring the team does not take it personally but instead uses it as a growth opportunity. Redirecting the conversation or avoiding the feedback creates an environment where issues are not resolved, directly affecting team progress and morale. Voting on the feedback's validity could further divide the team and does not encourage an atmosphere of openness and improvement. Developing new team agreements to avoid criticism does not ensure psychological safety; instead, it might stifle honest feedback, which is crucial for a team's development and success.

Scrum Retrospectives

PSM I - Scrum Retrospectives Example Questions

Question 1

Question 2

Question 3

Go Premium