The notion of pulling multiple stories into a Sprint is, AFAICT, based entirely on the notion that you’ll divvy up the stories between team members and work on them in parallel. 1/5
IMO, it’s much better for the whole team to work on each story in sequence using a collaborative technique like mob/ensemble programming. 2/5
If you do that, then it’s actually contraindicated to pull more than a single story because, if you do, you’re preventing other teams from working on the stories in your Sprint backlog. That guarantees that low value work is taking precedence over high-value work. 3/5
Of course, once you start working collaboratively on stories in sequence, the whole notion of a Sprint becomes far less interesting. 4/5
Shrinking the entire Sprint to a couple days (for one story) increases your meeting:work ratio entirely too much, and what’s the point of delaying reviews and retros until you complete a block of stories? 5/5
• • •
Missing some Tweet in this thread? You can try to
force a refresh
