or... we should demand that stakeholders actually plan what they want, and prototype the things they don't know if they need. Instead you turn everything into squares by lobbing off knubs, which takes time and effort, and rarely actually mitigates any of the changes chosen by people that are not programmers and not even competent people wishing to spend the time and effort to actually 'think' and 'plan' what the final product should in fact be at the start.... your puzzle pieces can be perfectly square, but if the picture of the end result of that puzzle changes, then you're pieces need to be thrown right in the trash and all the efforts making them were a waste of money and time. If you just want to collect a check, without constantly being at odds with the stakeholders, then agile and scrum makes sense... you offload the burden onto the stakeholders and let them play all day with cards which hopefully teach them the value of a story point... however, it's likely the worst way to actually ship good software, as it creates unperformant, overengineered, slop that is confused and not fit for its specific use, but only fit for being swapped out with some other code at a drop of the hat... code that again is unperformant, overengineered, slop not fit for its specific use.
or... we should demand that stakeholders actually plan what they want, and prototype the things they don't know if they need.
Instead you turn everything into squares by lobbing off knubs, which takes time and effort, and rarely actually mitigates any of the changes chosen by people that are not programmers and not even competent people wishing to spend the time and effort to actually 'think' and 'plan' what the final product should in fact be at the start.... your puzzle pieces can be perfectly square, but if the picture of the end result of that puzzle changes, then you're pieces need to be thrown right in the trash and all the efforts making them were a waste of money and time.
If you just want to collect a check, without constantly being at odds with the stakeholders, then agile and scrum makes sense... you offload the burden onto the stakeholders and let them play all day with cards which hopefully teach them the value of a story point... however, it's likely the worst way to actually ship good software, as it creates unperformant, overengineered, slop that is confused and not fit for its specific use, but only fit for being swapped out with some other code at a drop of the hat... code that again is unperformant, overengineered, slop not fit for its specific use.