Comments on: Software Project Success/Failure Criteria: Some Surprises by Robert L. Glass http://jfcouture.com/2006/07/12/software-project-successfailure-criteria-some-surprises-by-robert-l-glass/ Wed, 21 Mar 2012 09:32:48 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: djief http://jfcouture.com/2006/07/12/software-project-successfailure-criteria-some-surprises-by-robert-l-glass/#comment-207 djief Sat, 15 Jul 2006 18:15:40 +0000 http://www.jfcouture.com/?p=39#comment-207 Interesting link. It reminded that I need to read Steve McConnell latest book on software estimation (I've read all his other books and they are all excellent. "Code Complete" and "Rapid Development" should probably be used in every software engineering curricula.) You need comments on your blog Joel. Now. Interesting link. It reminded that I need to read Steve McConnell latest book on software estimation (I’ve read all his other books and they are all excellent. “Code Complete” and “Rapid Development” should probably be used in every software engineering curricula.)

You need comments on your blog Joel. Now.

]]> By: joelmig http://jfcouture.com/2006/07/12/software-project-successfailure-criteria-some-surprises-by-robert-l-glass/#comment-206 joelmig Fri, 14 Jul 2006 13:53:35 +0000 http://www.jfcouture.com/?p=39#comment-206 I guess you're right and none of those failure projects had successful estimations. I think the most important think about what Glass said was being able to adapt to the project needs. Development methodology must be closely appropriate to the application, requirements gathered at the time the decisions need to be made and management tight to day-to-day objectives. Jeff Atwood recently blogged about estimations in an interesting way (here's his last post about it: http://www.codinghorror.com/blog/archives/000627.html) I guess you’re right and none of those failure projects had successful estimations. I think the most important think about what Glass said was being able to adapt to the project needs. Development methodology must be closely appropriate to the application, requirements gathered at the time the decisions need to be made and management tight to day-to-day objectives.

Jeff Atwood recently blogged about estimations in an interesting way (here’s his last post about it: http://www.codinghorror.com/blog/archives/000627.html)

]]>