Top 10 Ways that Guarantee the Failure of a Project
I was reading an article about why projects fail and found interesting points and the following list has been inspired by actual mistakes encountered in real-world systems projects.
1. Don’t use a specific methodology because coding is all that is really important.
2. Create the project plan by working backwards from a drop-dead system completion date.
3. Don’t bother with a data model. Just build whatever tables you need.
4. Use a Technical Lead that has never built a similar system. Hiring such talent is too expensive.
5. Hire forty developers to make the coding go faster.
6. Selecting wrong tools and technologies for development
7. Three months before the system goes live, assign one junior developer to handle the data migration.
8. Skip the testing phase because the project is way behind schedule.
9. Change the system to support critical new requirements discovered during final development.
10. Buy a commercial, off-the-shelf package and customize it… a lot.