Enterprise Product Enterprise Product Implementation ProcessImplementation Process

Components of a Successful ImplementationComponents of a Successful Implementation

A detailed Scope Document for customer review and signoffA detailed Scope Document for customer review and signoff Creation of a detailed Project PlanCreation of a detailed Project Plan A working project team that includes the customerA working project team that includes the customer Weekly status reporting internally and to the customerWeekly status reporting internally and to the customer Weekly meetings with the customer driven by the project planWeekly meetings with the customer driven by the project plan Quality assurance and test planningQuality assurance and test planning Implementation review and participation by the customerImplementation review and participation by the customer

Enterprise Project Management ProcessEnterprise Project Management Process

Five Key PhasesFive Key Phases

InitiatingInitiating Sales process – Business Requirements Document (client signoff)Sales process – Business Requirements Document (client signoff)

PlanningPlanning Scope Document (client signoff)Scope Document (client signoff) Detailed Project PlanDetailed Project Plan

ExecutingExecuting Managing to the project planManaging to the project plan Project team/IT developing the system/productProject team/IT developing the system/product

ControllingControlling On-going status reporting and reviews with the customerOn-going status reporting and reviews with the customer

ClosingClosing Implementation and post-implementation reviewsImplementation and post-implementation reviews

Scope DocumentScope Document

Summarizes the project at a high levelSummarizes the project at a high level Requires customer review and signoff by both the customer and the Requires customer review and signoff by both the customer and the

companycompany Enables the company to better manage the customer in terms of Enables the company to better manage the customer in terms of

scope and enhancementsscope and enhancements Changes to an approved scope can lead to increased project Changes to an approved scope can lead to increased project

revenue in the form of project change orders required by the revenue in the form of project change orders required by the customercustomer

The scope should be developed prior to the project plan and receive The scope should be developed prior to the project plan and receive signoff prior to project implementationsignoff prior to project implementation

Additional changes should be added as addendums and Additional changes should be added as addendums and incorporated into the project planincorporated into the project plan

Components of the Scope DocumentComponents of the Scope Document

General project summaryGeneral project summary Description of components and capabilities of desired optionsDescription of components and capabilities of desired options Overview of project timelines and implementation datesOverview of project timelines and implementation dates Definition of roles and responsibilities from all organizations for the Definition of roles and responsibilities from all organizations for the

projectproject Assumptions that have been made during the scope definitionAssumptions that have been made during the scope definition Criteria/timing for acceptance of the project and deliverablesCriteria/timing for acceptance of the project and deliverables Approval section for scope signoff by the customer and the Approval section for scope signoff by the customer and the

companycompany

Project Planning & ExecutionProject Planning & Execution

Utilize the Scope Document, project team, product knowledge and Utilize the Scope Document, project team, product knowledge and IT process information to create a detailed, working project planIT process information to create a detailed, working project plan

Incorporate and schedule all tasks necessary for a successful Incorporate and schedule all tasks necessary for a successful implementationimplementation

Continually update the project plan to identify up-to-date project Continually update the project plan to identify up-to-date project statusstatus

Create customized views and reports from the project plan to aid in Create customized views and reports from the project plan to aid in status reviews with the project team and the customerstatus reviews with the project team and the customer

Weekly reporting to the customer identifying Progress, Planned Weekly reporting to the customer identifying Progress, Planned activities, Issues, and Action Items including dates and activities, Issues, and Action Items including dates and responsibilitiesresponsibilities

Customized reporting from the project plan to provide a detailed and Customized reporting from the project plan to provide a detailed and accurate view of the projectaccurate view of the project

The status report and the project plan drive the weekly status The status report and the project plan drive the weekly status meetings with the customermeetings with the customer

Quality AssuranceQuality Assurance

Risk analysis and management on an on-going basisRisk analysis and management on an on-going basis Quality reviews and milestones built into the project planQuality reviews and milestones built into the project plan Testing and signoff by a subset of the IT teamTesting and signoff by a subset of the IT team Review and approval of the product by the customer prior to Review and approval of the product by the customer prior to

implementationimplementation