{"id":998,"date":"2013-10-22T11:59:12","date_gmt":"2013-10-22T15:59:12","guid":{"rendered":"http:\/\/wehuberconsultingllc.com\/wordpress\/?p=998"},"modified":"2013-10-22T11:59:12","modified_gmt":"2013-10-22T15:59:12","slug":"the-mythical-man-month","status":"publish","type":"post","link":"https:\/\/wehuberconsultingllc.com\/wordpress\/2013\/10\/22\/the-mythical-man-month\/","title":{"rendered":"The Mythical Man Month"},"content":{"rendered":"

With the web site problems of www.healthcare.gov<\/a> dominating the news, I was reminded of the classic book on software project management from my era, The Mythical Man Month<\/a>. Surprisingly I found out that the first edition is available at archive.org<\/a>. I guess it is too late to recommend that someone in the Department of Health and Human Services read it before throwing more people at the project.<\/p>\n

Some people might argue that a book written in 1975 is not relevant to today\u00e2\u20ac\u2122s project managers. Well, here is a shorter IEEE article, Why Software Fails<\/a>, written in 2005 that echoes a lot of the same sentiments. If we believe the www.healthcare.gov<\/a> reporting is accurate then this project has already exhibited many of the factors that should cause the project<\/a> to fail. Read it and weep! In that article the authors say:<\/p>\n

\n

Why do projects fail so often?<\/b><\/p>\n

Among the most common factors:<\/p>\n