Comment on Why overplanning makes projects fail?parentComments−goalieca1yOver-planning often comes from a place of management wanting observability and predictability. They want to be in control and know all the risks.This ends up inversing all of the agile Manifesto.* Individuals and interactions over processes and tools* Working software over comprehensive documentation* Customer collaboration over contract negotiation* Responding to change over following a plan−steveBK1231y* Customer collaboration over contract negotiationThis is a bad assumption for the agile premise in many large non tech orgs. Many cases internal tech tools just do not have users with this mindset.Here’s what I wanted, why isn’t it already this way, go fix it, stop showing me stuff that isn’t done yet.Or the other flavor where every touch point changes their feature of the week such that you are always behind what they actually want.It’s entirely possibly to iterate such that no one is happy with delivery.
Comments
Over-planning often comes from a place of management wanting observability and predictability. They want to be in control and know all the risks.
This ends up inversing all of the agile Manifesto.
* Individuals and interactions over processes and tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiation
* Responding to change over following a plan
* Customer collaboration over contract negotiation
This is a bad assumption for the agile premise in many large non tech orgs. Many cases internal tech tools just do not have users with this mindset.
Here’s what I wanted, why isn’t it already this way, go fix it, stop showing me stuff that isn’t done yet.
Or the other flavor where every touch point changes their feature of the week such that you are always behind what they actually want.
It’s entirely possibly to iterate such that no one is happy with delivery.