The Past
- April 2013 (1)
- March 2013 (2)
- November 2012 (3)
- October 2012 (2)
- December 2011 (1)
- November 2011 (2)
- October 2011 (2)
- January 2011 (2)
- October 2010 (2)
- September 2010 (5)
- June 2010 (1)
- June 2009 (2)
- April 2009 (1)
- March 2009 (2)
- December 2008 (1)
- November 2008 (1)
- October 2008 (3)
- June 2008 (2)
- May 2008 (1)
- April 2008 (3)
- March 2008 (1)
- February 2008 (4)
- January 2008 (5)
- December 2007 (1)
- November 2007 (1)
- October 2007 (2)
- September 2007 (4)
- June 2007 (2)
- May 2007 (1)
- April 2007 (3)
- March 2007 (3)
- February 2007 (4)
- January 2007 (3)
- November 2006 (1)
- October 2006 (1)
- September 2006 (3)
- August 2006 (3)
- June 2006 (1)
- May 2006 (2)
- April 2006 (3)
- March 2006 (2)
- February 2006 (9)
- January 2006 (2)
- December 2005 (5)
- November 2005 (8)
- October 2005 (5)
- September 2005 (7)
- August 2005 (4)
- July 2005 (3)
- June 2005 (5)
- May 2005 (6)
- March 2005 (10)
- February 2005 (3)
- January 2005 (4)
- December 2004 (7)
- November 2004 (8)
- October 2004 (6)
- September 2004 (5)
- August 2004 (7)
One Response
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.
Interesting find. The writer (and posters) of the article seems to be gravitating around the idea of the Software Manager (PM, whatever) to be the center of the project’s universe. Nothing is further from the truth. I guess it’s a more complex issue, and yes, having an inadecuate manager will contribute to the problem. However, most of the problems we encounter relating to Software reliability and project failures are due to the lack of understanding of the business rules to be implemented (IMHO). What is now called Requirements Engineering – Perhaps req. eng. is not the solotion, just as OO wasn’t the solution to the software building issues, but, it’s much better than what it was a few years back.
For a concrete example of what I mean, read how NASA build software systems: everything is written in paper and must be peer reviewed – Every line of code is designed, accounted for, and audited. Of course, there are problems, as nothing is 100% reliable. However, they have managed to do a very good job at what we call Software Engineering.