26 Ways To Know Your Software Development Project Is Doomed

Does any of these sound familiar to you?

• The project name changes for the third time in as many months.
• The requirements definition is begun four months after development started.
• The developer doesn't understand the spec document and continues to develop anyway. And the QA team doesn't know how to test, but they "test" anyway.
• The user or client requests new features instead of focusing on bug fixing and performance enhancements.
• The technical project manager asks you to compose the list of user requirements—without consulting any actual potential users.
• Status reports are seen as insubordinate.
• You learn that management had to insist that the interface definitions be checked into version control after the first code freeze.
• The QA team is told, "We've only allocated three weeks for testing" (on a project that has lasted six months already). Or QA is told, "The date is fixed. We have to have all this functionality by that date."
  

Want to see the entire list? Go to http://www.cio.com/article/470103/_Ways_To_Know_Your_Software_Development_Project_Is_Doomed

On the other side, there are Ten Tips for Running Successful Projects: http://www.projectsmart.co.uk/ten-tips-for-running-successful-projects.html

And more … Make or Break: Why Accurate Cost Estimation Is Key: http://www.projectsmart.co.uk/make-or-break-why-accurate-cost-estimation-is-key.html