Sprint planning: "Let's commit to exactly what we're going to deliver over...
Sprint planning: "Let's commit to exactly what we're going to deliver over the next 2 weeks."
That's a problem. Why? Because that's not how software development works.
We realize what’s most useful to do next on a MUCH shorter time horizon.
Often daily. Or even hourly.
🧵👇
Real dev goes like this:
“I hit a blocker.”
“I can’t do x until y.”
“If I do x first, doing y will be quicker."
So avoid "rigid" sprints. Respond to change. Be agile.
Pulling new work into a sprint isn’t reason for concern. It’s just a sign the team is learning and iterating.