msgbartop
News, views, tips and tricks on Oracle and other fun stuff
msgbarbottom

Top 10 Ways to Know Your Software Project is Doomed

Here is my top 10 from this list of 101 ways to know your software project is doomed:

  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.

What’s your favorite one?


Filed in ColdFusion, Oracle on 27 Aug 07


Reader's Comments

  1. |

    I choose the #2 ;D

  2. |

    Number 10 is the best 😀

  3. |

    6 is a little close to home 😛

  4. |
    1. No comments in the code because if it was hard to write, it should be hard to figure out.

    2. Developers are responsible for ALL testing.

    This following is absolutely true. My day begins with a 1/2 hour status meeting everyday. My day ends with a 1 hour status meeting everyday. On tuesdays we have an extra 1 hour status meeting in addition to the 1 1/2 hours we are already meeting everyday.

    That’s 8.5 hours per week on status. Better than 1/5 of the entire week (for a 40 hour week. bwahahahahaha.)

    On some days, I have to stop what I am doing to respond to status emails “that must be responded to immediately”. That’s usually during testing.

    Welcome to my world.

    LewisC

  5. |

    I head a team of four developers. We have been very busy with a major migration project. We have to “go live” with the new version beginning of November.

    I was like you Lewis, spending many hours every week simply reporting on our progress…. until my boss realized two things: 1- It is very hard to track progress on a micro level. 2- If we continue losing precious time on reporting our progress, we’ll miss the deadline.

    So, all what we have now is a lunch meeting, every Friday for a couple of hours to report status and plan for the following week.

  6. |

    5 Your manager wastes 7 hours a week asking for progress reports

    –Only 7 hours a week? Actually, number 6 is my favorite, because that’s what supervisors will say.

  7. |

    Ohh! Iike this point very much : The last book you read: Oracle 8i A Beginner’s Guide.

    it helps not to run into new errorful features!! And you are compatible to almost all database releases!!! 🙂

    And : Developers are not responsible for any testing

    The opposite is dangerous too. If the future user group of the system does not test and only developers do.

    Karl