You are on page 1of 12

The formula for implementation success: Pervasive’s Rapid Implementation Methodology. Repeatable. Reliable. Proven.

............... Physical Construction .........................................287.............................. Support Handoff ......................................... Analysis .............................................................. Quality Assurance Testing.......................................................................................... 11 Step 10................................... 8 Step 5............ Discovery/Design Phase...........com .......................................................... 9 Step 7.... 3 I..................................... 3 Methodology Structure............................ 5 Step 2......... 10 Step 8........... 9 III........... 4 Step 1........... 9 Step 6... Customer Acceptance ............................... Project Review................................................ 10 Step 9................................................... 6 Step 3................800...........4383 Page 2 of 12 proserv@pervasive....................................................... Detailed Analysis and Design Discovery ...........................Introduction ....... Customer Proposal Review and Acceptance ....................... 11 Pervasive Professional Services Engagement Flow Chart 12 Copyright 2004 Pervasive Software Pervasive Professional Services 1.................................. Implementation Phase ...... 6 Step 4....... Design / Project Plan ..................... Acceptance Phase....... Pre-Project Assessment ........................ 7 II.............................

Quality Assurance III. encompass a total of ten steps: I. the Pervasive Rapid Implementation Methodology.com . Customer Support Interchange 10. enabling customers to make use of as much or as little support as they need – from discovery to design to implementation and beyond. These are the components that make PRIMe flexible enough to scale to many different types and sizes of data infrastructure projects. Analysis 3. Pre-Project Assessment / Discovery 2. Its modularity and flexibility ensure system scalability. Copyright 2004 Pervasive Software Pervasive Professional Services 1. while its repeatability and reliability guarantee results every time. Discovery Phase 1. This expertise has enabled the development of a codified process for ensuring implementation success: PRIMe™. honed in implementation and training services that span 20 years and 35. PRIMe describes the system that Pervasive Professional Services employs to power successful implementation of data infrastructure projects. Post Project Review Each of the ten PRIMe steps may include one or more substeps.Introduction Pervasive® Professional Services brings to bear a deep knowledge base. while speeding customer velocity to value for fast ROI. Design / Project Plan 4. Detailed Analysis and Discovery 6. Customer Project Acceptance 9. Methodology Structure PRIMe is based on hierarchical levels. Acceptance Phase 8.287.000 customers around the world. comprised of three phases.4383 Page 3 of 12 proserv@pervasive. Implementation Phase 5. in turn. Customer Proposal Review and Acceptance II.800. PRIMe is an in-depth and flexible methodology that promotes total understanding of data infrastructure projects. which. Physical Implementation 7.

definition and objectives of the project. Discovery/Design Phase The Discovery/Design phase is dedicated to understanding the customer’s requirements.4383 Page 4 of 12 proserv@pervasive. The complete project plan and proposal are presented to the customer for acceptance.I. which includes a plan that identifies resources and dependencies for the project. This phase requires reiterative contact with the customer.com . Analysis -Verify Business Process Flow -Identify Logistics Constraints -Identify Project Priorities -Identify Project Risks Request Customer Feedback Design -ID Previous Solution Leverage -Document High Level Solution -Design from Architect -Document Refined Solution Project Plan -ID Required Resources -Map Milestones to Project Plan -ID Dependent Tasks -Refine Time Constraints Request Customer Feedback Customer Proposal -Review Design with Customer -Review Plan with Customer -Articulate Success Criteria -Gain Acceptance from Customer Copyright 2004 Pervasive Software Pervasive Professional Services 1. to capture project business objectives and to record and validate project requirements.800. with the goal of producing a project plan and proposal. Discovery / Design Phase Flow Diagram Pre-Project Assessment -Discovery Resources Assigned -Project Introduction from Sales -Turnover Briefing from SEs -Review of existing documents Customer Discovery -Pervasive Professional Services introductions to Customer -Identify Pervasive Professional Services Customer Contact -Review of Pre-Project Efforts Request Customer Feedback -Strengthen Customer Reqmts. A design is formulated.287.

com .287. Review business process flow H.) • Value Prompter (if applicable) • Prior demonstration and discovery meeting notes • Business process flow diagram • Functional/technical requirements document • Operational design specification • Data and metadata samples • Customer environment specifications (OS. Relevant files/collateral/documentation – • Legal documentation (MPSA. Establish best communication methods with customer Copyright 2004 Pervasive Software Pervasive Professional Services 1. etc.4383 Page 5 of 12 proserv@pervasive.800. etc.Step 1. Identify Pervasive Professional Services resources • Project Manager • Project Lead B. Verify facts contained in existing documents F. Strengthen customer requirements I. Pre-Project Assessment Pervasive Professional Services assigns appropriate team members to review discovery collateral and participate in the discovery meeting. Document customer assumptions / expectations G. Recommended estimates of effort E. NDA. Objectives of the Pre-Project Assessment / Discovery step are: A. Recommended solution design • High-level design document • Design notes D.) • Programming language preference • Field level mapping document C. This interaction is used for introductions and identifying the key participants and identify high level requirements. The discovery portion represents the initial contact with the customer and Pervasive Professional Services. network.

3. A team design review should be held with the architect. Objectives of the Design / Project Plan Step are: 1. Identify previous IP that can be leveraged Document a high level solution Architect review solution with team Produce refined design for customer review Document Project test Plan Define high level project tasks Define project milestones to gauge progress Identify and assign appropriate Pervasive Professional Services resources for all project tasks 9.Step 2. Identify and communicate project success measures 10. 2. 4. Teams and individuals should be invited to attend where applicable. Define a project communication plan Copyright 2004 Pervasive Software Pervasive Professional Services 1. The objectives of the Analysis step are: 1.4383 Page 6 of 12 proserv@pervasive. 5.287. SE and Support. 6.800. Secure acceptance of deliverables 13. 2. 3. Analysis Pervasive Professional Services will conduct an in-depth analysis of the project documents. Design / Project Plan Based on the analysis of the technical collateral and results of Discovery. Identify project risk factors 11. 6. These documents will serve as attachments to the proposal (SOW). Pervasive Professional Services will document the proposed solution design in a Solution Design Document and/or Diagram. 7. Results of this analysis will be documented and serve as the basis for refining the design of the solution. The Pervasive Professional Services Project Manager will receive the design from the Pervasive Professional Services Architect.com . 5. The PM will then use the design along with the other documents generated thus far to create the overall project plan. 4. Verify business/political/financial challenges and constraints Understanding of the customer’s logistical/resource/timeframe List functional requirements of solution Document the technical challenges Document priorities of the solution Identify and document project risks Step 3. 8. Generate Project Change Requests (PCR) as required 12.

800. Location where services will be performed (onsite. QA test plan 7. 5. These documents will then be considered a legal part of the contract and will hold all parties accountable. 8. 2. 7. Defined project rate structure Acceptance Proposal is supplied to the sales account manager. and a contingency plan 9. noneditable (PDF preferred) Sales representative delivers proposal to customer Customer reviews and signs proposal (authorized signature required) Customer faxes proposal to sales representative Sales representative delivers proposal for Pervasive CFO signature Sales representative returns copy signed proposal to customer Proposal considered accepted Copyright 2004 Pervasive Software Pervasive Professional Services 1. Acceptance Process for Acceptance: 1. 6. 4. Customer Proposal Review and Acceptance Proposal The proposal is generated and accompanied by the relevant documentation defined in the proposal checklist. 3. This occurs before the formal proposal is generated.4383 Page 7 of 12 proserv@pervasive.com . The results of the design and project planning sessions serve as the basis to generate a proposal. Statement of Work • Definition of the deliverables • Definition of the project tasks • Assumptions made during the development of the plan 3. Acceptance of the proposal is based on the client returning a signed copy of the proposal along with an acceptable means of payment (i. Definition of team members required to complete the project 5. Production implementation plan. Basic solution description 2. Proposed plan is reviewed with the sales account manager to re-qualify the client. remote. Project Plan • Dependencies for each project task and deliverable • Proposed date for project milestones and project completion 6. Pervasive Professional Services management produces proposal draft Sales management review and approve Proposal document is locked down.e.287. or both) 4. 9. Purchase Order). Delivery plan (including knowledge transfer and training) 8.Step 4. Proposal Checklist 1.

Pervasive Professional Services team members will be assigned to complete the project. Implementation Phase Flow Diagram Change Requests -Return to Discovery -Project Plan and -Design Modified From Discovery Phase Detailed Analysis and Design Discovery -Design Details Documented -Maps / Processes / Code Flow -Architect Review of Final Design Request Customer Feedback Physical Construction -Engineers Begin Coding -PM Maps Milestone Progress -PM correlates SOW Deliverables -PM Manages Change Requests Quality Testing -Testing Environment Completed -Design Test Plan Implemented -Functionality Verified -Performance Optimization Copyright 2004 Pervasive Software Pervasive Professional Services 1. too.800. includes extensive feedback from the customer. Details for the code.287. During construction.com . milestone deliverables are reviewed with the customer. or processes to be created are documented. Implementation Phase Upon execution of the proposal.II.4383 Page 8 of 12 proserv@pervasive. Deliverables requiring change outside the scope of the project are identified and appropriate change requests are submitted to the customer for acceptance. Areas requiring more information are clarified by working with the customer to resolve the unknown and mitigate risks. This phase. maps. The engineers review the approved design documents.

3. Verify functional requirements are met per SOW deliverables Verify operational requirements via defined test plan Verify optimal performance Document results of testing in a customer report Page 9 of 12 1.4383 proserv@pervasive. The project may require Pervasive Professional Services to define. The level of testing required for a given deliverable will be defined in the SOW. 2. 2. Deliverables are managed by version control software. Physical Construction Pervasive Professional Services constructs the project deliverables according to the design specifications and functional requirements defined in the SOW.com Copyright 2004 Pervasive Software Pervasive Professional Services . Detailed Analysis and Design Discovery Pervasive Professional Services identifies the detail specifications and requirements for the project. Objectives of the Physical Construction step: 1. Any deviations from the test plan should be documented and communicated to the customer and project team. Any issues that are identified during the construction phase which require additional billable hours must be communicated via the Project Manager to the customer and documented in a PCR. 2. Objectives of Quality Assurance Testing step: 1. All the detail should be documented and communicated to the customer. 3. Construct deliverables according to SOW Perform module / unit testing as construction permits Document actual construction steps Document interface anomalies and work around Maintain version integrity of deliverables Manage scope of project Step 7. A PCR may be required to adjust the SOW or deliverables or Project timeline. 5. 3. Quality Assurance Testing Pervasive Professional Services will test the quality of each of the project deliverables. 5. 6.287. Objective of Detailed Analysis and Design Discovery step: 1. 6. construct a functional. 4. 4.800.Step 5. unit and or system level test plan for each deliverable. Verify design assumptions from Discovery phase Define detailed field mapping Define detailed event / process flows Define interface details for embedded projects Review final design with architect Submit any plan changes to customer Make plan changes if required Step 6. 4. 7.

800. 2.287. Acceptance Phase Flow Diagram Customer Acceptance -Documentation Completed -Knowledge Transfer Delivered -Production Rollout Completed Support Handoff -Support Engineers Briefed -Project Documentation to Support Post Project Review -Project Success Review -Leverage IP Archived -Process Change Suggestions Step 8. knowledge transfer and production rollout.com .III. General and specific knowledge transfer sessions will also be defined in the SOW. Objectives of the Customer Acceptance step: 1. Customer Acceptance The Customer Acceptance phase includes three distinct substeps: documentation. Produce or collect all levels of documentation Present product training if defined in SOW Hold knowledge transfer sessions with customer Assist. The level of documentation provided with each deliverable will be defined explicitly in the SOW. 4. Acceptance Phase The acceptance phase consists of three steps. if customer requests.4383 Page 10 of 12 proserv@pervasive. that the customer can receive world-class support and that new best practices identified are implemented. which ensure that the project deliverables have been completed. Finally. the SOW explicitly defines Pervasive Professional Services role in the solution deployment to production. in rolling solution into production Copyright 2004 Pervasive Software Pervasive Professional Services 1. 3.

Hold project overview session with support engineers 3.287. and engineering Document suggested process improvement steps ©2004 Pervasive Software Inc. The objective of the review is to refine future solutions and incorporate the knowledge gained on the project into future designs and project plans.4383 Page 11 of 12 proserv@pervasive.com . SEs. 2. During this session the project team provides the client contact info and client team roles. Provide support with customer contact/role list Step 10. Objectives of Support handoff step: 1. All Pervasive brand and product names are trademarks or registered trademarks of Pervasive Software Inc. Objectives of Project Review step: 1. Project Review The project team conducts de-brief with SE and technical Support teams. Support Handoff The project team conducts a de-brief session with Pervasive technical support. 3. Transfer documentation to support access area 2. in the United States and other countries. 4. All rights reserved. Document best practices exposed in this project Catalog IP that maybe leveraged in future products Distribute technical “discoveries” to support.800.Step 9. All other marks are the property of their respective owners. Copyright 2004 Pervasive Software Pervasive Professional Services 1. The session should include a review of the project documentation and a deliverables-specific knowledge transfer session.

PSG PSG\TSD Pipeline Entry Sales \ SE \ PSG \ Support Project Handoff Conference Call PSG Gather Additional Info PRIMe Acceptance Phase No PSG Enough Info Yes PSG Document Findings Pervasive Statement of Work delivered to customer for review and signature.800. Go to Sales PSG Scope Change PRIMe Discovery and Design Phase PRIMe Implementation Phase Pervasive Professional Services 1. Go to Sales Yes Copyright 2004 Pervasive Software Sales \ PSG Review and Qualify PSG Project Assignment Resource Briefing Yes No SOW/PCR Accepted Sales Qualified? Yes Sales \ PSG Submit and Negotiate PSG Proposal No Go to Sales Pervasive Project Change Request delivered to customer for review and signature.287. PSG Viable Project? Pervasive Project Acceptance Document delivered to customer for review and signature.4383 proserv@pervasive.From Sales PSG Engagement Flow Chart End of Process Page 12 of 12 Sales \ SE \ PSG \ Support Incorporate Changes As Necessary Sales \ SE PSG \ Support Project Review Lessons Learned PSG \ Support Technical Handoff Customer Sign-Off PSG Project Implementation PSG Generate PCR Submit and Negotiate PSG Proposal Sales \ SE \ PSG \ Support Technical Handoff Pervasive Master Services Agreement delivered to customer for review and signature.com .