Top 10 Ways to Know Your Software Project is Doomed
Here is the top 10 list Eddie selected from his 101 ways to know your software project is doomed post:
1. Developers use the excuse of “self documenting code†for no comments
2. All of your requirements are written on a used cocktail napkin
3. Progress is now measured by the number of fixed bugs and not completed features
4. Your source code control system is a series of folders on a shared drive
5. Your manager wastes 7 hours a week asking for progress reports
6. The phrase “It works on my machine†is heard more than once a day
7. Developers are not responsible for any testing
8. All code reviews are scheduled a week before product launch
9. You have cut and pasted code from The Daily WTF
10. The last book you read: Oracle 8i A Beginner’s Guide.
