1. Enterprise Product Implementation Process

2. Components of a Successful Implementation  A detailed Scope Document for customer review and signoff  Creation of a detailed Project Plan  A working project team that includes the customer  Weekly status reporting internally and to the customer  Weekly meetings with the customer driven by the project plan  Quality assurance and test planning  Implementation review and participation by the customer

3. Enterprise Project Management Process Five Key Phases  Initiating  Sales process – Business Requirements Document (client signoff)  Planning  Scope Document (client signoff)  Detailed Project Plan  Executing  Managing to the project plan  Project team/IT developing the system/product  Controlling  On-going status reporting and reviews with the customer  Closing  Implementation and post-implementation reviews

4. Scope Document  Summarizes the project at a high level  Requires customer review and signoff by both the customer and the company  Enables the company to better manage the customer in terms of scope and enhancements  Changes to an approved scope can lead to increased project revenue in the form of project change orders required by the customer  The scope should be developed prior to the project plan and receive signoff prior to project implementation  Additional changes should be added as addendums and incorporated into the project plan

5. Components of the Scope Document  General project summary  Description of components and capabilities of desired options  Overview of project timelines and implementation dates  Definition of roles and responsibilities from all organizations for the project  Assumptions that have been made during the scope definition  Criteria/timing for acceptance of the project and deliverables  Approval section for scope signoff by the customer and the company

6. Project Planning & Execution  Utilize the Scope Document, project team, product knowledge and IT process information to create a detailed, working project plan  Incorporate and schedule all tasks necessary for a successful implementation  Continually update the project plan to identify up-to-date project status  Create customized views and reports from the project plan to aid in status reviews with the project team and the customer  Weekly reporting to the customer identifying Progress, Planned activities, Issues, and Action Items including dates and responsibilities  Customized reporting from the project plan to provide a detailed and accurate view of the project  The status report and the project plan drive the weekly status meetings with the customer

7. Quality Assurance  Risk analysis and management on an on-going basis  Quality reviews and milestones built into the project plan  Testing and signoff by a subset of the IT team  Review and approval of the product by the customer prior to implementation