3 ms·
Indeed. Development should not begin until all requirements have been finalized. Every project I've ever been on that had wildly wrong estimates was because ma
by sublinear 3y ago
Indeed. Development should not begin until all requirements have been finalized.
Every project I've ever been on that had wildly wrong estimates was because management didn't actually plan jack shit either due to inexperience, laziness, malice, or all of the above. They then play the blame game to try to keep their job, and man it's so hilarious to witness the sheer carnage as everyone tears them a new asshole nowadays with the rise work from home (group chats/calls, DMs, etc.)
We seriously need to drain the swamp of inept management and nepotism within business ranks.
I've experienced better and it is absolutely possible to be off by less than ~25% of the total time estimated.
i.e. it took 6 days instead of 5, or it took 5 months instead of 4, which is way less depressing.
- JohnFen 3y ago> Development should not begin until all requirements have been finalized. I agree, but this runs directly counter to Agile methodologies which are all the rage these days.
- imtringued 3y ago"How to end up shipping your project three years after the planned release"-starter-kit.