Build Your Enterprise Application Implementation Playbook

Your implementation doesn’t start with technology, but with an effective plan that the team can align on.

RETIRED CONTENT

Please note that the content on this page is retired. This content is not maintained and may contain information or links that are out of date.

Not putting together an effective playbook will:

  • Cause the implementation team to put in place something that isn’t aligned with what the organization needs.
  • Lead to a greater number of difficult-to-resolve issues with stakeholders and the project sponsor.
  • Lead to a greater chance for the overall implementation to fail.

Building your Enterprise Application Implementation Playbook enables you to:

  • Keep the end in mind, maintaining focus on what is most important in the implementation phase.
  • Identify the stakeholders and sponsors up front before getting started.
  • Defining the scope, steps, and approach in a manner that enables quick alignment on your approach for implementation.

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.

Module 1: Understand the Project

The Purpose

Lay out the overall objectives, stakeholders, and governance structure for the project.

Key Benefits Achieved

Align everyone on the sponsor, key stakeholders, vision, and goals for your project

Activities: Outputs:
1.1 Select the project sponsor.
  • Project sponsor has been selected.
1.2 Identify your stakeholders.
  • Project stakeholders have been identified and mapped with their roles and responsibilities.
1.3 Align on a project vision.
  • Vision has been defined.
1.4 List your guiding principles.
  • Guiding principles have been defined.
1.5 Confirm your goals and objectives for the implementation project.
  • Articulated goals and objectives.
1.6 Define the project governance structure.
  • Detailed governance structure.

Module 2: Set up for Success

The Purpose

Define the elements of the playbook that provide scope and boundaries for the implementation.

Key Benefits Achieved

Align the implementation team on the scope for the project and how the team should operate during the implementation.

Activities: Outputs:
2.1 Gather and review requirements, with an agreed to scope.
  • Requirements for enterprise application implementation with an agreed-to scope.
2.2 Define metrics for your project.
  • Metrics to help measure what success looks like for the implementation.
2.3 Define and document the risks that can impact the project.
  • Articulated list of possible risks during the implementation.
2.4 Establish team composition and identify the team.
  • The team responsible and accountable for implementation is identified.
2.5 Detail your OCM structure, resources, roles, and responsibilities.
  • Details of your organization’s change management process.
2.6 Define requirements for training.
  • Outline of training required.
2.7 Create a communications plan for stakeholder groups and delivery teams.
  • An agreed-to plan for communication of project status.

Module 3: Document Your Plan

The Purpose

With the structure and boundaries in place, we can now lay out the details on the implementation plan.

Key Benefits Achieved

A high-level plan is in place, including next steps and a process on running retrospectives.

Activities: Outputs:
3.1 Define your implementation steps.
  • An agreed to high-level implementation plan.
3.2 Create templates to enable follow-up throughout the project.
  • Follow-up templates to enable more effective follow-ups.
3.3 Decide on the tracking tools to help during your implementation.
  • Shortlist of tracking tools to leverage during the implementation.
3.4 Define the follow-up processes.
  • Defined processes to enable follow-up.
3.5 Define project progress communication.
  • Defined project progress communication.
3.6 Create a Change request process.
  • A process for managing change requests.
3.7 Define your retrospective process for continuous improvement.
  • A process and template for running retrospectives.
3.8 Prepare a closure document for sign-off.
  • A technique and template for closure and sign-off.
Visit our Exponential IT Research Center
Over 100 analysts waiting to take your call right now: 1-519-432-3550 x2019