101 Ways To Know Your Software Project Is Doomed

Published 07-19-2007 7:54 PM | barakoboy

got this from my boss today.  my personal favorites: 17, 36, and 100 (best of the lot)

  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 “*** 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’
  11. Ever iteration meeting starts with “Do you want the good news or the bad news…”
  12. Your team still gives a crap about its CMM Level
  13. Progress is now measured by the number of fixed bugs and not completed features
  14. Continuous Integration is getting new employees to read the employee handbook
  15. You are friends with the janitor
  16. The SCRUM master doesn’t really care what you did yesterday or what you will do today
  17. Every milestone ends in a dead sprint
  18. Your best developer only has his A+ Certification
  19. You do not understand the acronyms DRY, YAGNI, or KISS; but you do understand WTF, PHB, and FUBAR
  20. Your manager could be replaced by an email redirection batch file
  21. The only certification your software process has is ISO 9001/2000
  22. Your manager thinks ‘Metrics’ is a type of protein drink
  23. Every bug is prioritized as Critical
  24. Every feature is prioritized as Trivial
  25. Project estimates magically match the budget
  26. Developers use the excuse of ’self documenting code’ for no comments
  27. Your favorite software pattern is God Object
  28. You still believe compiling is a form of testing
  29. Developers still use Notepad as an IDE
  30. Your manager wastes 7 hours a week asking for progress reports (true story)
  31. You do not have your own machine and you are not doing pair programming
  32. Team Rule - No meetings until 10 AM since we were all here until 2 AM
  33. Your team believes ORM is a ‘fad’
  34. Your team believes the transition from VB6 to VB.NET will be ’seamless’
  35. Your manager thinks MS Project is the best management tool the market offers
  36. Your spouse only gets to see you on a webcam
  37. None of your unit tests have asserts in them
  38. FrontPage is your web page editor of choice
  39. You get into flame wars if { should be on new line, but you are impartial to patterns such as MVC
  40. The company motto is ‘Do more with less’
  41. The phrase ‘It works on my machine’ is heard more than once a day
  42. The last conference your .NET team attended was Apple WWDC 2000
  43. Your manager insists that you track all activity but never uses the information to make decisions
  44. All debugging occurs on the live server
  45. Your manager does not know how to check email
  46. Your manager thinks being SOX compliant means not working on baseball nights
  47. The company hires Senetor Ted Stevens to give your project kick-off inspiration speech
  48. The last book you read - Visual InterDev 6 Bible
  49. The overall budget is mistaken for your weekly Mountain Dew bill
  50. Your manager spends his lunch hour crying in his car (another true story)
  51. Your lead web developer defines AJAX as a cleaning product
  52. Your boss expects you to spend the next 2 days creating a purchase request for a $50 component
  53. The sales team decreased your estimates because they believe you can work faster
  54. Requirement - Rank #1 on Google
  55. Everyday you work until Midnight, everyday your boss leaves at 4:30
  56. Your manager loves to say “Why do the developers care? They get paid by the hour.”
  57. The night shift at Starbucks knows you by name
  58. Management can not understand why anyone needs more than a single monitor
  59. Your development team only uses source control as a power failure backup system
  60. Developers are not responsible for any testing
  61. The team does not use SVN because they believe the merge algorithms are black voodoo magic
  62. Your white boards are mostly white (VersionOne)
  63. The client continually mistakes your burn-down chart for a burn-up chart
  64. The project code name is renamed to ‘The Death March’
  65. Now it physically pains you to say the word - Yes
  66. Your teammates don’t refactor, they refuctor
  67. To reward you for all of your overtime your boss purchases a new coffee maker
  68. Your project budget is entered in the company ledger as ‘Corporate Overhead’
  69. You secretly outsource pieces of the project so you can blog at work
  70. A Change Control Board is created and your product isn’t even its first alpha version
  71. Daily you consider breaking your fingers for the short term disability check
  72. The deadline has been renamed a ‘milestone’…just like the last ‘milestone’
  73. Your project managers ‘open door’ policy only applies between 5:01 PM - 7:59 AM
  74. Your boss argues “Why buy it when we can built it!”
  75. You bring beer to the office during your 2nd shift
  76. The project manager is spotted consulting a Ouija board
  77. You give misinformation to your teammates so you look better on your personal review
  78. All code reviews are scheduled a week before product launch
  79. Budget for testing exists as “if we have time”
  80. The client will only talk about the requirements after they receive a fixed estimation
  81. The boss does not find the humor in Dilbert
  82. You start noticing your boss’s poker tells during planning poker
  83. You start wondering if working 2 shifts at Pizza Hut is a better career alternative
  84. All performance issues are resolved by getting larger machines
  85. The project has been demoted to being released as a permanent ‘Beta’ version
  86. Your car is towed from the office parking lot as it was thought to be abandoned
  87. The project manager likes to doodle during requirements gathering meetings
  88. Your SCRUM team consists of 1
  89. Your timesheet looks like a Powerball ticket
  90. The web developer thinks being 508 means looking good in her Levi Red Tabs
  91. You think you need Multiple Personality Disorder medication because you are Mort, Elvis, and Einstein
  92. Your manager substitutes professional consultant advice for a Magic 8 Ball
  93. You know exactly how many compile warnings cause an ‘Out of Memory’ exception in your IDE
  94. I have used IDE twice in this list and you still don’t know what it stands for
  95. You have cut and pasted code from The Daily WTF
  96. Broken unit tests are deleted because they are obviously out of date
  97. You are sent to a conference to learn, but you skip sessions to go hunting for swag
  98. QA has nicknamed you Chief Off-By-One
  99. You are using MOSS 2007
  100. You have been 90% complete 90% of the time
  101. “Oh, oh, and I almost forgot. Ahh, I’m also gonna need you to go ahead and come in on Sunday, too… thanks”

Comments

# University Update-AJAX-101 Ways To Know Your Software Project Is Doomed said on July 19, 2007 6:48 AM:

Pingback from  University Update-AJAX-101 Ways To Know Your Software Project Is Doomed

# rdagumampan said on July 19, 2007 3:59 PM:

elow barakoboy,

the original link can be found here www.codesqueeze.com/101-ways-to-know-your-software-project-is-doomed. I suggest just put a reference to the link and not the whole contents of the entry. Thanks.

# lamia said on July 19, 2007 6:12 PM:

Here are my picks:

14.Continuous Integration is getting new employees to read the employee handbook

19.You do not understand the acronyms DRY, YAGNI, or KISS; but you do understand WTF, PHB, and FUBAR

26.Developers use the excuse of ’self documenting code’ for no comments

27.Your favorite software pattern is God Object

28.Your manager wastes 7 hours a week asking for progress reports (true story)

29.Your team believes ORM is a ‘fad’

35.Your manager thinks MS Project is the best management tool the market offers

43.Your manager insists that you track all activity but never uses the information to make decisions

44.All debugging occurs on the live server

54.Requirement - Rank #1 on Google

62.Your white boards are mostly white (VersionOne)

65.Now it physically pains you to say the word - Yes \

67.To reward you for all of your overtime your boss purchases a new coffee maker

83.You start wondering if working 2 shifts at Pizza Hut is a better career alternative

91.You think you need Multiple Personality Disorder medication because you are Mort, Elvis, and Einstein

What is wrong with MOSS 2007?

99.You are using MOSS 2007

Is there an opensource alternative to Sharepoint?

# barakoboy said on July 19, 2007 8:06 PM:

@dehran ph  thanks for the link and the tip!  :D

@lamia hmmm sharepoint not really sure if there is

# raseryu said on July 23, 2007 2:07 AM:

No offense to my current company... But I could really relate with no.2. HAHA

# lamia said on July 30, 2007 1:55 AM:

There seems to be an opensharepoint.sourceforge.net

# Greg Moreno said on November 11, 2007 12:28 AM:

101. You work with a project using PHP in the morning, using Java in the afternoon, and you're boss expects you to finish the two before you leave.

# dynamic Reflections said on May 29, 2010 6:38 AM:

Ok, my pace is still slow. This time, a three week vacation is the excuse. I'm sad, returning to work does not make me sad, but while taking a peek to my rss feeds I noticed this article about doom ...