I've found them incredibly useful for getting teams to be realistic about their bandwidth and throughput. They bring data to conversations and help engineers, d

I've found them incredibly useful for getting teams to be realistic about their bandwidth and throughput. They bring data to conversations and help engineers, designers, and PMs put actual numbers to decisions and trade-offs. I think the formality of sprints is way overblown, but the cadence of them can be extremely valuable. Having stakeholders come together to discuss and tweak plans is super helpful. Ideally, _tweak_ is the keyword. If you have major changes sprint-to-sprint, something else is wrong. In most cases, the discussion goes something like this: * (A) We're on track. Everything is going well. Here's what's outstanding. If we get that done, what do we want to stretch for? * (B) We've had some problems/things aren't moving as fast as we thought. Here's why. What should we do about it.