Govern and Manage an Enterprise Software Implementation

Don’t outsource your brain. You can’t outsource project accountability to the SI.

Unlock

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.

Speak With A Representative Sign In
or Call: 1-888-670-8889 (US) or 1-844-618-3192 (CAN)

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

Govern and Manage an Enterprise Software Implementation

1

Determine project rationale

See if COTS process optimization makes sense.

3

Enter plan/analyze phase

Adequately prepare for the overall project and gather requirements. Conduct a stage-gate assessment of the phase.

4

Enter design phase

Prepare for overall software project design. Conduct a stage-gate assessment of the phase.

5

Enter build phase

Build the solution in a manner that meets identified requirements. Conduct a stage-gate assessment of the phase.

6

Enter test/deploy phase

Thoroughly evaluate that the deployed solution is meeting business objectives. Conduct a stage-gate assessment of the phase.

Info-Tech Academy

Get Info-Tech Certified

Train your staff and develop a world-class IT team.

New to Info-Tech Academy? Learn more here

Enterprise App Select and Implement Course

Don’t outsource your brain: You can’t outsource project accountability to the SI.
This course makes up part of the Applications Certificate.

Now Playing: Executive Brief

Course information:

Title: Enterprise App Select and Implement Course
Number of Course Modules: 5
Estimated Time to Complete: 2-2.5 hours

Featured:
Suanne McGrath-Kelly, Sr. Research Director, Applications Practice
David Piazza, VP of Research & Advisory, Applications Practice

Onsite Workshop

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 roadmap in place to complete your project successfully.

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.

  • Large Software Implementation Maturity – Project Risk Level
  • Preliminary Project Governance Structure

1.2

Establish project guiding principles.

  • Preliminary Project Guiding Principles

1.3

Large Software Implementation Maturity Assessment Tool completed and results discussed.

1.4

Establish change management procedures.

  • Change Request Accommodation Criteria
  • Change Request 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.

  • List of lessons learned from previous software implementation project
  • Draft of risks and proposed mitigating actions

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.

  • List of lessons learned from previous software implementation project
  • Draft of risks and proposed mitigating actions

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.

  • List of lessons learned from previous software implementation project
  • Draft of risks and proposed mitigating actions

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.

  • List of lessons learned from previous software implementation project
  • Draft of risks and proposed mitigating actions

Search Code: 76101
Published: October 6, 2014
Last Revised: October 6, 2014