If a team insists that big Stories cannot be split into smaller ones, how would the Scrum Master coach them to do otherwise?

A. Suggest a story-splitting boot camp in the next IP iteration

B. Invite a development manager to emphasize the importance of splitting Stories

C. Demonstrate Story-splitting techniques using a specific example

D. Emphasize the SAFe principles to highlight the importance of flow

The most effective approach among the options provided for a Scrum Master to coach a team that insists big Stories cannot be split into smaller ones is:

C. Demonstrate Story-splitting techniques using a specific example.

Why Demonstrate Story-splitting techniques using a specific example is correct

1. Practical Learning: Demonstrating story-splitting techniques with a specific example provides a hands-on, practical learning experience. It helps the team understand how even complex, large stories can be decomposed into smaller, manageable parts that fit within an iteration. This method directly addresses the team’s concerns or misconceptions about the indivisibility of Big Stories.


2. Immediate Relevance: Using a specific example, especially one from the team’s current backlog, makes the exercise immediately relevant and applicable. It shows the team how the concepts apply to their work, increasing the likelihood of acceptance and understanding.


3. Encourages Collaboration: This approach fosters a collaborative environment where the team can discuss and contribute to the story-splitting process. It encourages team members to share ideas and learn from each other, building a stronger, more cohesive team dynamic.

Why the other options are not as effective?

A. Suggest a story-splitting boot camp: in the next IP iteration: While educational, suggesting a boot camp might be seen as too theoretical or removed from the day-to-day challenges the team faces. It may also delay addressing the immediate need to split big Stories for ongoing or upcoming sprints.

B. Invite a development manager to emphasize the importance of splitting Stories: This approach might come across as authoritative and could potentially create resistance. It might make the team feel pressured or undermined, rather than empowered to learn and apply a new technique.

D. Emphasize the SAFe principles to highlight the importance of flow: While understanding SAFe (Scaled Agile Framework) principles is important, simply emphasizing these principles without practical guidance on how to apply them to story splitting might not be effective. It could be too abstract for teams struggling with the practical aspects of splitting stories.

By focusing on practical demonstration (option C), the Scrum Master can effectively guide the team through the perceived barrier, showing them that it is possible and beneficial to split big Stories into smaller, more manageable pieces. This approach directly addresses the problem and provides immediate, actionable solutions.

Other SAFe Scrum Master Question – Which two Framework elements would a Scrum Master have the strongest connection and most frequent interaction? (Choose two.)