Comments on: Top 10 Ways to Know Your Software Project is Doomed http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/ News, views, tips and tricks on Oracle and other fun stuff Thu, 18 Mar 2010 16:44:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Karl Reitschuster http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/comment-page-1/#comment-51471 Karl Reitschuster Sat, 01 Sep 2007 07:13:49 +0000 http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/#comment-51471 <p>Ohh! Iike this point very much : The last book you read: Oracle 8i A Beginner’s Guide.</p> <p>it helps not to run into new errorful features!! And you are compatible to almost all database releases!!! :-)</p> <p>And : Developers are not responsible for any testing</p> <p>The opposite is dangerous too. If the future user group of the system does not test and only developers do.</p> <p>Karl</p> 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

]]> By: maxCohen http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/comment-page-1/#comment-51457 maxCohen Thu, 30 Aug 2007 13:53:44 +0000 http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/#comment-51457 <p>5 Your manager wastes 7 hours a week asking for progress reports</p> <p>--Only 7 hours a week? Actually, number 6 is my favorite, because that's what supervisors will say.</p> 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.

]]> By: Eddie Awad http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/comment-page-1/#comment-51449 Eddie Awad Wed, 29 Aug 2007 02:32:19 +0000 http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/#comment-51449 <p>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.</p> <p>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.</p> <p>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.</p> 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.

]]> By: LewisC http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/comment-page-1/#comment-51448 LewisC Wed, 29 Aug 2007 00:51:17 +0000 http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/#comment-51448 <ol> <li><p>No comments in the code because if it was hard to write, it should be hard to figure out.</p></li> <li><p>Developers are responsible for ALL testing.</p></li> </ol> <p>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.</p> <p>That's 8.5 hours per week on status. Better than 1/5 of the entire week (for a 40 hour week. bwahahahahaha.)</p> <p>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.</p> <p>Welcome to my world.</p> <p>LewisC</p>

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

  • 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

    ]]>         By: Tony Fendall http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/comment-page-1/#comment-51437 Tony Fendall Tue, 28 Aug 2007 04:15:45 +0000 http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/#comment-51437 <p>6 is a little close to home :P</p> 6 is a little close to home :P

    ]]>         By: fatih batuk http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/comment-page-1/#comment-51434 fatih batuk Mon, 27 Aug 2007 12:02:35 +0000 http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/#comment-51434 <p>Number 10 is the best :D</p> Number 10 is the best :D

    ]]>         By: Francois http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/comment-page-1/#comment-51433 Francois Mon, 27 Aug 2007 11:00:07 +0000 http://awads.net/wp/2007/08/27/top-10-ways-to-know-your-software-project-is-doomed/#comment-51433 <p>I choose the #2 ;D</p> I choose the #2 ;D

    ]]>