The more things change, the more they stay the same….. As part of client work that I am involved with, I have been interviewing other companies that have SharePoint installed and are actually using it as a document management system. I have a set of questions that I send to the...
http://www.pmsolutions.com/collateral/research/Strategies%20for%20Project%20Recovery%202011.pdf Similarly, an often quoted report from the Standish Group called the Chaos Report cites ten key factors for a challenged project and none of the ten factors includes or blames the software product itself as the primary reason for project failures. And one final reference from a presentation by Bob Lawhorn of CAI in March 2010 about the causes of challenged projects: Poorly defined applications (miscommunication between business and IT) contribute to a 66% project failure rate, costing U.S. businesses at least $30 billion every year (Forrester Research) 60% – 80% of project failures can be attributed directly to poor requirements gathering, analysis, and management (Meta Group) 50% are rolled back out of production (Gartner) 40% of problems are found by end users (Gartner) 25% – 40% of all spending on projects is wasted as a result of re-work (Carnegie Mellon) Up to 80% of budgets are consumed fixing self-inflicted problems (Dynamic Markets Limited 2007 Study) If we agree, for the sake of argument, that the software is not typically the problem, that leaves us with the other two corners of this triangle – the customer or the system integrator
But while the statistics behind IT project failures is widely reported, the devil is in the details as to why many of these projects fail
This in turn leads to potential project failure or less than anticipated results
RISK of ECM Project Failure Say “risk of ECM project failure” in a board room and you quickly discover that the most scary scenario is a performance related failure discovered after a go-live deployment to production, yet it happens all the time
So, how do you avoid disappointed users and project failure on a records or content management solution?
When you weigh your alternatives’ Pros and Cons, a solution that gets you only 80% of what you want but can be almost certainly executed beats the solution that gets you 100% of what you want – but has a significant risk of project failure and big negative impact when it does
This is often the single biggest cause of ECM project failure. When we consider that the change required to succeed with many core use-cases for ECM (for example, moving from a "File / Save As…" world to the need to add metadata to a simple MS Office document), there is little wonder end users will often rebel
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use