tag:blogger.com,1999:blog-1314610166729912649.post6099907185022680965..comments2012-09-25T23:13:44.048-07:00Comments on Stop Blaming the Software! Avoiding IT Project Failure through Corporate Profiling : IT Project Failure - The Root Causes behind every Reason for IT Project FailureProfilingProhttp://www.blogger.com/profile/08697195725680574092noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1314610166729912649.post-85517911383397563312009-09-29T12:56:28.479-07:002009-09-29T12:56:28.479-07:00I think PM Hut makes a good point, however, I stil...I think PM Hut makes a good point, however, I still think that although senior managers are capable of visualizing the benefits of a new system, they often don't realize how complex implementations can become.<br />Their all to often "Ready, Fire, Aim" approach where premature decisions are made is the starting point of an IT project disaster.<br />Sure, they should have communicated more effectively but with whom?<br />This brings me to my point.<br />Before communicating, they need to take a hard look at who the affected parties in their organization are that need to be involved or not.<br />This is at the all-important pre-investment stage when management needs to make sure that they have gained support for their project and that the affected parties are fully committed and accountable for their roles in the implementation.<br />Often this is not the case and the parties pay lip-service (poor communications in this case being a symptom of bad planning and not the cause).<br />Anyway, I think we're both on the same wave-length.<br />Cheers, Mark.Anonymoushttps://www.blogger.com/profile/11672515816154397085noreply@blogger.comtag:blogger.com,1999:blog-1314610166729912649.post-5074829052217016652009-09-29T12:15:59.415-07:002009-09-29T12:15:59.415-07:00I like your article on Scapegoating (linked from h...I like your article on Scapegoating (linked from here).<br /><br />Now about IT Project Failure, I think there is one root cause for all the reasons behind project failure, which is lack of communication. You can think of any reason, and you can easily find that the root cause is lack of communication.<br /><br />Let's say the reason is we used ASP instead of PHP, and ASP is proprietary and the client does not want to pay for a proprietary software. Had the requirements been gathered properly from the client (lack of communication) that would've not been a problem.<br /><br />Another example is "The interface is not usable". Again, had there been a constant communication with the client and his/her end users that would've not been a problem.<br /><br />I cannot think of any example, whether related to the client, the stakeholders, or the team where the root cause is the lack of communication.<br /><br />PS: check this article on why <a href="http://www.pmhut.com/most-it-projects-fail-will-yours" rel="nofollow">most IT projects fail</a>.PM Huthttp://www.pmhut.comnoreply@blogger.com