How should the team handle an oversized user story in Sprint Planning?
WHAT IT TESTS: Protecting the Sprint Goal when a story is too big. ANSWER OUTLINE: Split it vertically with the Product Owner, swarm the top slice, and renegotiate scope rather than overcommitting. RED FLAG: Proposing overtime or horizontal splits.
WHAT IT TESTS: Whether the candidate protects the Sprint Goal over rigid completion, showing mastery of scope negotiation and vertical splitting. ANSWER OUTLINE: First, collaborate with the Product Owner to split the story vertically into thin, end-to-end slices; second, pull only the highest-priority slice into the sprint and swarm on it; third, renegotiate remaining scope instead of overcommitting. RED FLAG: Recommending overtime, sequential handoffs between developers, or horizontal layer splits.
Read the original → agilealliance.org
- #agile
- #scrum
- #sprint-planning
- #story-splitting
- #estimation
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.