During Iteration Review, the team decides to carry forward three stories to the next Iteration. This is the second time during this PI that some of the team's stories are carried over. What are two actions the Scrum Master should take? (Choose two)

Choose one or more of the following:

• Coach the team to honor their commitments
• Take a 'wait and see' approach because the team assures they are still on track for the PI
• Discuss the issue at the next Iteration Retrospective
• See if the Product Owner is agreeable to moving the stories into the next Iteration
• Perform the 5 Whys to identify the root cause of all delays

Why this is the correct answer

Carrying forward stories to the next iteration can be an indication of a problem that needs to be addressed. When the team carries over stories multiple times during a PI, it can indicate a recurring issue that requires attention. In this scenario, the Scrum Master should take two actions: discuss the issue at the next Iteration Retrospective and perform the 5 Whys to find the root cause of all delays.

Discussing the issue at the next Iteration Retrospective is an effective way to bring the problem to the team's attention and facilitate a conversation about how to address it. During the Retrospective, the team can reflect on the causes of the issue, brainstorm solutions, and come up with a plan to prevent it from happening again in the future. By involving the entire team in this conversation, the Scrum Master can ensure that everyone is aware of the problem and invested in finding a solution.

Performing the 5 Whys to find the root cause of all delays is another useful tool for the Scrum Master. By asking "why" five times, the Scrum Master can help the team drill down into the underlying causes of the issue. This process can reveal deeper problems that are contributing to the team's struggles and help the team identify targeted solutions to address the root cause of the problem. By using this technique, the Scrum Master can help the team understand the underlying issues and develop a plan to address them effectively.

In conclusion, when the team carries over stories multiple times during a PI, the Scrum Master should take action to address the issue. By discussing the issue at the next Iteration Retrospective and performing the 5 Whys to find the root cause of all delays, the Scrum Master can help the team identify the underlying problems and develop a plan to address them effectively. These actions can help the team to improve their performance and deliver more consistent results in the future.