My personal favourites taken from 101 Ways To Know Your Software Project Is Doomed.
- Developers use the excuse of “self documenting code” for no comments
- All of your requirements are written on a used cocktail napkin
- Progress is now measured by the number of fixed bugs and not completed features
- Your source code control system is a series of folders on a shared drive
- Your lead web developer defines AJAX as a cleaning product
- Developers are not responsible for any testing
- All code reviews are scheduled a week before product launch
- Every bug is prioritized as Critical
- Every feature is prioritized as Trivial
- The night shift at Starbucks knows you by name
- To reward you for all of your overtime your boss purchases a new coffee maker
- The lead web developer thinks the X in XHTML means ‘extreme’
- Ever team meeting starts with “Do you want the good news or the bad news…”
The sad part is how many of these actually ring true for real projects in real organizations.