PROJECT RESCUE & RECOVERY PRACTICE
-
Health Audit – Only with a full diagnostic of the program/project can we determine how best to begin the RCA. Our Health Audit is the first step in discovering there is a problem.
-
Root Cause Analysis (RCA) – With a project trending outside of acceptable levels, various troubled symptoms will start to appear. Let’s not react until we find out the true root cause of the trouble. Symptoms are alerts of deeper problems; here we will uncover those true problems.
-
Rescue & Recovery Plan – When charting new territory, you best have a roadmap to guide you. Recovering a troubled project is always new territory and the development of our plan will ensure all members of the team clearly understand what is about to transpire.
-
Implementation of Recovery – Let us guide you through the change required to return your projects to acceptable levels by implementing the agreed upon recovery plan. A highly efficient and effective change management process will be used during this stage of recovery.
-
Monitoring & Controlling the Change – Close monitoring and correcting of behaviors, actions, tasks, and reporting is needed to measure the successfulness of the project recovery. It is in this stage your stakeholders will want to see the metrics pointing to a positive outcome.
-
Lessons Learned – While lessons learned are important after every project, nowhere are they more important than after recovering a troubled project. This exercise will guide the entire team though a positive learning experience to ensure this kind of trouble never strikes again.
Rescue Data Sheet
As YOUR project recovery team:
According to the annual Chaos Report published by the Standish Group, in the US alone there are approximately 175,000 IT projects inflight with a combined budget of $250 billion.
-
31.1% will be canceled
-
52.7% will end up costing 189% of the original budget
-
Only 16.2% will be completed on-time and on-budget
The Chaos Report goes on to say the top 3 reasons for project failure are as follows:
-
Lack of User Input – 12.8%
-
Incomplete Requirements and Specifications – 12.3%
-
Changing Requirements and Specifications – 11.8%
Almost 37% of all failed IT projects have nothing to do with the technology. 36.9% of all failed projects can be avoided by partnering with a strong organization that knows how to identify and determine your requirements, communicate them to all levels of stakeholders, and manage those requirements throughout the project.
RESCUE MY PROJECT™
METHODOLOGY:
Our Services can often include a wide
range of specialized offerings.The MTI Project Recovery Practice centers around six key areas for which our leadership team fields the most demand.
BENEFITS
Engaging MTI’s Rescue My Project™ methodology gives your organization peace of mind knowing that a leading expert in the industry is an integral part of your strategic team to save your project investment (time, money, and team moral) from ultimate failure. Let us work with you to recover!