First people incorrectly equate agility (the ability to change) to scrum, kanban, or some other small batch method for building software.
Someone told them they’ll get work done faster.
They notice scrum (or kanban) has more frequent checkpoints (stage transitions) than waterfall because of the small batches.
Finally they make the critical mistake here and think small batches are something that primarily benefits measuring and forecasting.
Accountability every release? Yay!
In reality using small batches makes it harder to forecast which is why that’s not the point of it!
The point of small batches is to make changing direction easier.
As soon as the focus is on measuring, the team is actually dissuaded from changing.
People become motivated to make the actual time reported to complete work follow their predictions.
They are also motivated to build what was forecasted for future sprints and not to modify the backlog based on feedback (don’t upset prior commitments to scope!).
If they’re going to do that they’re better off with waterfall.
Just my opinions ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Totally agree and see this happen too often.
First people incorrectly equate agility (the ability to change) to scrum, kanban, or some other small batch method for building software.
Someone told them they’ll get work done faster.
They notice scrum (or kanban) has more frequent checkpoints (stage transitions) than waterfall because of the small batches.
Finally they make the critical mistake here and think small batches are something that primarily benefits measuring and forecasting.
Accountability every release? Yay!
In reality using small batches makes it harder to forecast which is why that’s not the point of it!
The point of small batches is to make changing direction easier.
As soon as the focus is on measuring, the team is actually dissuaded from changing.
People become motivated to make the actual time reported to complete work follow their predictions.
They are also motivated to build what was forecasted for future sprints and not to modify the backlog based on feedback (don’t upset prior commitments to scope!).
If they’re going to do that they’re better off with waterfall.
Just my opinions ;)