I’m surprised by some of the comments on this, but the SAFe logo is kind of like a bat signal for trolls. So maybe not surprised at all.
Spillover is just a symptom. We pay attention to it, but not to blindly prevent it from occurring. Instead, we care to see if its usage points to systemic barrier to agility… or if it enhances how we posture ourselves to deliver value better.
Example 1. The team’s Sprint Goals have been achieved, and an ambitious developer pulls in another story beyond the original commitment. The story will spillover, and will likely be ready for test early in the next sprint.
Example 2. The product owner continuously ignores the team’s capacity, and adds more stories to the sprint. Lower priority items continue to get pushed to future sprints.
In both scenarios, spillover isn’t the issue; it’s the context and reasons behind it that matter. Instead of focusing on spillover itself, we should be attentive to the processes and behaviors that lead to it.
Anyone want to venture into a discussion about which example represents the negative scenario that needs attention?
Unlock the secrets to conquering story spillover in Scrum! Discover why it happens and how to prevent it. https://lnkd.in/d2rbX_gi
Get insights on managing uncertainty and complexity, and find out what's an acceptable variation in sprint planning. Watch this video by Naveen Kumar Singh to learn more about achieving the perfect sprint goal.
#ScrumSuccess #StorySpilloverSolutions #AgileMastery
Sr. Events Manager at Scaled Agile, Inc.
1wSo excited to have LSA as one of our Large Soltion Sponsors! Looking forward to the amazing things you will showcase at your booth.