101 Ways to know your project is doomed

Here I only list the top 10…
you may find the rest of the list here.

    1. Management has renamed its Waterfall process to Agile Waterfall
    2. You start hiring consultants so they can take the blame
    3. The Continuous Integration server has returned the error message “Fuck it, I give up”
    4. You have implemented your own Ruby framework that uses XML configuration files
    5. Your eldest team member references Martin Fowler as a ’snot-nosed punk’
    6. Your source code control system is a series of folders on a shared drive
    7. Allocated QA time is for Q and A why your crap is broken
    8. All of your requirements are written on a used cocktail napkin
    9. You start considering a new job so you don’t have to maintain the application you are building
    10. The lead web developer thinks the X in XHTML means ‘extreme’