3 ms·
> Sprints are for having a fast feedback + adjustments loop with a customer whose needs are unclear Do they add any value there compared to having the same cad
by dragonwriter 3y ago
> Sprints are for having a fast feedback + adjustments loop with a customer whose needs are unclear
Do they add any value there compared to having the same cadence of customer contact, while dev happens in a flow-based (kanban, etc.) model with as-ready delivery of value-producing units of work (i.e., stories) as completed?
I get that historically sprints were adopted as a way to do incremental, fast-feedback delivery as an alternative to “deliver at the end” project styles, and as an alternative to that, they seem to make sense. But they still incorporate the “deliver at the end” mindset, just with arbitrarily timeboxed aggregates of what is otherwise conceived as independent units of work. And if you’ve got independent, value-delivering units of work, its not too long until you realize that those are your natural and irreducible “deliver at the end” units.
- datadrivenangel 3y agoKanban is the way. Keep things flowing.
- jraph 3y ago> having the same cadence of customer contact, while dev happens in a flow-based (kanban, etc.) model with as-ready delivery of value-producing units of work (i.e., stories) as completed? I'm currently on a project that works like this, without sprints, and clearly it works for us. Also, no standups. We communicate as soon as it's needed and not more (often) than needed.
- fnordpiglet 3y agoPlanning should be a continuous and real time endeavor; and planning without your stakeholders input is a plan to fail.
- SkyPuncher 3y agoI'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.
- CSMastermind 3y ago>I get that historically sprints were adopted as a way to do incremental, fast-feedback delivery as an alternative to “deliver at the end” project styles, and as an alternative to that, they seem to make sense. The root of most of what we call 'Agile' today goes back to a method for managing difficult clients when doing (primarily web development) consulting. If you're not a consultant or you're not trying to defensively manage a difficult client then it's a poor set of processes for your development work to follow.