Govern and Manage an Enterprise Software Implementation
Don’t outsource your brain: You can’t outsource project accountability to the SI.
This content requires an active subscription.
Access this content by logging in with your Info-Tech Research Group membership or contacting one of our representatives for assistance.
Your Challenge
You have been tasked with delivering a large-scale software implementation project. Historically, similar projects within your organization have failed to complete on time, on budget, and/or have failed to deliver upon their intended benefits. It some cases, these projects have even been abandoned altogether. With a new project on the horizon, you need to minimize your risks of repeat failure.
Our Advice
Critical Insight
- Even in today’s day and age, where information sharing is easier than it has ever been, large-scale software projects continue to fail at an alarming rate (an average of 66% over budget, 33% over time, and delivered with 17% less value than originally predicted, according to a recent publication by McKinsey & Company). Although most companies will survive a failed software implementation, 17% of the failed projects researched can essentially threaten the existence of an organization.
- One would think that IT shops would have such implementations down to a science; however, these “black swan” projects (defined as projects that exceed 200% in budget overruns), occur a lot more than what would be expected.
- You have solicited the professional services of a systems integrator. You want to ensure that you are able to manage the SI, and aren’t solely dependent upon their methodology throughout the implementation period.
Impact and Result
- Assuming greater accountability over the project (avoid over-reliance on the SI)
- Leveraging the collective knowledge and advice of other IT professionals
- Reviewing common pitfalls and lessons learned from failed implementations
- Proper risk mitigation planning for each stage of the project
- Self-assessment of your own readiness to enter/exit each stage of the project
Want to Participate in Our Research?
- Analyst Interviews: Share your best practices, opinions, tools or templates with your peers.
- Webinars: Interactive session to keep us focused on topics you want to tackle.
- Upcoming Workshops: Accelerate your project with an onsite, expert analyst to facilitate a workshop for you. Contact us for more details.
Get the Complete Storyboard
See how all the steps you need to take come together, with tools and advice to help with each task on your list.
Download NowGet to Action
-
Determine project rationale
See if COTS process optimization makes sense.
-
Prepare for the project
Determine appropriate project governance.
-
Enter plan/analyze phase
Adequately prepare for the overall project and gather requirements.
-
Exit plan/analyze phase
Conduct a stage-gate assessment of the phase.
-
Enter design phase
Prepare for overall software project design.
-
Exit design phase
Conduct a stage-gate assessment of the phase.
-
Enter build phase
Build the solution in a manner that meets identified requirements.
-
Exit build phase
Conduct a stage-gate assessment of the phase.
-
Enter test/deploy phase
Thoroughly evaluate that the deployed solution is meeting business objectives.
-
Exit test/deploy phase
Conduct a stage-gate assessment of the phase.
Guided Implementation
This guided implementation is a four call advisory process.
-
Call #1: Enter plan/analyze phase entry and exit readiness reviews
- Once you have reviewed the common pitfalls, created your risk mitigation plan, and self-evaluated against the entry criteria, we can help review your plan, discuss any of your concerns, and validate your readiness for entry into the Plan/Analyze phase.
- Once you approach the closure of the phase and have self-evaluated against the exit criteria for Plan/Analyze, we can discuss any lessons learned, and validate your readiness for exiting the Plan/Analyze phase.
-
Call #1: Enter design phase entry and exit readiness reviews
- Once you have reviewed the common pitfalls, created your risk mitigation plan, and self-evaluated against the entry criteria, we can help review your plan, discuss any of your concerns, and validate your readiness for entry into the Design phase.
- Once you approach the closure of the phase and have self-evaluated against the exit criteria for Design, we can discuss any lessons learned, and validate your readiness for exiting the Design phase.
-
Call #1: Enter build phase entry and exit readiness reviews
- Once you have reviewed the common pitfalls, created your risk mitigation plan, and self-evaluated against the entry criteria, we can help review your plan, discuss any of your concerns, and validate your readiness for entry into the Build phase.
- Once you approach the closure of the phase and have self-evaluated against the exit criteria for Build, we can discuss any lessons learned, and validate your readiness for exiting the Build phase.
-
Call #1: Enter test/deploy phase entry and exit readiness reviews
- Once you have reviewed the common pitfalls, created your risk mitigation plan, and self-evaluated against the entry criteria, we can help review your plan, discuss any of your concerns, and validate your readiness for entry into the Test/Deploy phase.
- Once you approach the closure of the phase and have self-evaluated against the exit criteria for Test/Deploy, we can discuss any lessons learned, and validate your readiness for go-live.
Guided Implementation #1
Guided Implementation #2
Guided Implementation #3
Guided Implementation #4
Onsite Workshop
Module 1: Prepare for Project Launch
The Purpose
- Workshop introduction.
- Preview of the two days.
- Overview of governance, guiding principles, and implementation maturity.
Key Benefits Achieved
- Created a process for defining implementation guiding principles and governance structures.
- A frank assessment of your historical COTS implementation maturity.
| Activities: | Outputs: | |
|---|---|---|
| 1.1 | Establish project governance structure. |
|
| 1.2 | Establish project guiding principles. |
|
| 1.3 | Large Software Implementation Maturity Assessment Tool completed and results discussed. |
|
| 1.4 | Establish change management procedures. |
|
Module 2: Plan/Analyze
The Purpose
- Overview of Plan/Analyze phase.
- Discuss lessons learned from the Plan/Analyze phase of the previous software implementation projects.
- Discuss common risks and pitfalls experienced during the phase.
- Compile risks and propose mitigating actions.
- Develop a methodology for future projects in the Plan/Analyze phase.
Key Benefits Achieved
- Bring a structured approach to the plan and analyze phases of an enterprise software implementation project.
| Activities: | Outputs: | |
|---|---|---|
| 2.1 | Build plan/analyze team. |
|
| 2.2 | Determine activities. |
|
| 2.3 | Identify lessons learned. |
|
Module 3: Design
The Purpose
- Overview of design phase.
- Discussion on lessons learned from the design phase of the previous software implementation projects.
- Discussion on common risks and pitfalls experienced during the phase.
- Compile risks and propose mitigating actions.
- Develop a methodology for future projects in the design phase.
Key Benefits Achieved
- Bring a structured approach to the design phase of an enterprise software implementation project.
| Activities: | Outputs: | |
|---|---|---|
| 3.1 | Build design team. |
|
| 3.2 | Determine activities. |
|
| 3.3 | Identify lessons learned. |
|
Module 4: Build
The Purpose
- Overview of build phase.
- Discuss lessons learned from the build phase of the previous software implementation projects.
- Discuss common risks and pitfalls experienced during the phase.
- Compile risks and propose mitigating actions.
- Develop a methodology for future projects in the design phase.
Key Benefits Achieved
- Bring a structured approach to the build phases of an enterprise software implementation project.
| Activities: | Outputs: | |
|---|---|---|
| 4.1 | Create build team. |
|
| 4.2 | Determine activities. |
|
| 4.3 | Identify lessons learned. |
|
Module 5: Test/Deploy
The Purpose
- Overview of test/deploy phase.
- Discuss lessons learned from the test/deploy phase of the previous software implementation projects.
- Discuss common risks and pitfalls experienced during the phase.
- Compile risks and propose mitigating actions.
- Develop a methodology for future projects in the test/deploy phase.
Key Benefits Achieved
- Bring a structured approach to the test and deploy phases of an enterprise software implementation project.
| Activities: | Outputs: | |
|---|---|---|
| 5.1 | Build test/deploy team. |
|
| 5.2 | Determine activities. |
|
| 5.3 | Identify lessons learned. |
|
Book Your Workshop
Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.
Book NowProject Management Map
-
1Drive Organizational Change from the PMO
-
2Tame the Project Backlog
-
3Define and Deploy an Enterprise PMO
-
4Create Project Management Success
-
5Develop a Project Portfolio Management Strategy
-
6Grow Your Own PPM Solution
-
7Optimize Project Intake, Approval, and Prioritization
-
8Manage a Minimum-Viable PMO
-
9Govern and Manage an Enterprise Software Implementation
-
10Develop a Resource Management Strategy for the New Reality
-
11Select and Implement a PPM Solution
-
12Enhance PPM Dashboards and Reports
-
13Focus on Project Management Essentials
-
14Avoid Project Management Pitfalls
-
15Increase Throughput by Driving Completion and Closure
-
16Set a Strategic Course of Action for the PMO in 100 Days
-
17
Empower Decision Makers Through a Project Portfolio Office
Search Code: 76101
Published: October 6, 2014
Last Revised: October 6, 2014
