6 ms·
I have seen many failed or very expensive projects. An unordered list of issues. 1. Sunk cost. Quit before it hurts. 2. Non-technical leaders. Talk to experts
by AtNightWeCode 3y ago
I have seen many failed or very expensive projects. An unordered list of issues.
1. Sunk cost. Quit before it hurts.
2. Non-technical leaders. Talk to experts when it comes to tech. I don't care if you watched a Youtube-vid.
3. Tech people that think they know it all. Don't build waste that solves problems that the business does not have.
4. Person cult. Anybody can make simple mistakes.
5. Department cult. Quit pretending that the guys at your department are smarter.
6. No scope. Define what to do.
7. No order. Prioritize what is important.
8. Premature or upfront decisions. Why create time estimates first and then figure out what to do.
9. Cowboys. Crazy time estimates that someone high up in the hierarchy just made up without talking to anybody.
10. Everything tech. Not sure why, but some dev teams can't add a simple feature without rebuilding half the tech stack. Features are built on current stack. Tech is built with tech decisions but may be necessary to add a feature.
11. Overlapping. Multiple people doing the same work.
12. Bad architecture. Architecture that does not simplify anything.