Implementation Methodologies

Methodology Life Cycle :
Tasks & Activities by Phase :

JAD/Discovery Sessions :

  1. The JAD Sessions will consist of in-person interviews with the Field Trip Planning Software project team comprised of representatives of each department that will be using the new system.
  2. The purpose of the BPR is to establish the key business processes and relationships that will guide the implementation process.
  3. Your key project stakeholders should participate in the BPR in order to optimize the system's configuration.
  4. Depending upon the size and scope of the project, an Executive BPR session may be conducted. Its purpose is to gather key stakeholders from all affected lines of business to discuss strategic topics and make high-level decisions for the project. These include items like:
    • Strategic goals & objectives for project
    • Establish project governance model
    • Establish high-level requirements across the enterprise
    • Finalize project rollout strategy
    • Establish policy for the application sharing model (I.e. who can see what)
    • Identify integration requirements
    • Develop adoption / change management & communication plans

Plan & Design Deliverables [PD Pack] :

  1. At the conclusion of the Plan and Design Phase, Consulting team will publish a Plan and Design Pack (PD) for client approval and sign off.
  2. The PD Pack provides the overall design and detailed scope and will be used as a blue print for the building and testing of the solution.
  3. The PD packet will consist of the following documents:
    • Requirements document
    • Security Matrix
    • Fit-Gap Spreadsheet
    • Functional/Technical Design Document
    • Technical Architecture Document
    • Data Architecture and Data Mapping Document
    • Use Cases and Test Cases
    • Deployment Plan
Plan & Design Deliverables :
Document Description
Requirements Document System Requirements from Business Stakeholders Website and CRM.
Configuration Guide Business Rules and Set up Information for Salesforce.
Conference Room Pilot 1 and Pilot 2 Conference room Pilot 1 after configuration is complete and Pilot 2 after Development is complete.
Security Matrix User roles, profiles and data level access is defined.
Fit-Gap Spreadsheet Identifies the gaps in functionality that need to be built on the Force.com platform. Also, identifies the business processes that are a fit for Salesforce.
 Functional Design List detailed functional design of what needs to be developed on Force.com platform. The FD document identifies current & future business processes,, business rules and screen layouts for custom screens.
Use Cases Use Cases describe "who" can do "what" with the solution. The Use Case is used to capture a system's behavioral requirements based on Scenarios.
Technical Architecture Documents the overall Technical Architecture of the solution including interactions with 3rd party apps, online portals and home grown systems.
Technical Design Technical Design of all customizations on the Force.com platform. The Technical design document will be updated during the Configure & Deploy Phase.
Data Architecture Design & Migration Plan Defines the specific data to be migrated to the new solution The Data Migration Plan also outlines the overall approach from working with the client, to getting the data, to verifying the integrity of the migration process.
Integration Framework Defines integration points with 3rd party systems and how it will be accomplished.
Configure & Develop Deliverables :
Document Description
Test Plan Defines the overall approach to Quality Assurance and documents the specific testing process and test scripts.
Deployment Plan Documents the overall approach and plan for deploying the solution to production. This document also defines the process for migrating custom code and functionality.
Data Mapping Document Detailed Field Level Mapping between FS360 and 3rd party systems.
Technical Design Document Technical Design Document for all custom code will be enhanced during this phase. High level Pseudo code will be added to all design documents with proper comments.
Test, Train, and Deploy Deliverables :
Document Description
CRP (Conference Room Pilot) CRP provides the client with an opportunity to see a subset of the functionality early in the process and provide feedback and clarification.
UAT Plan User Acceptance Testing (UAT) Plan describes the overall approach to UAT with Participants, entry and exit criteria, approval process and timelines. UAT plan will be done by the Client.
Support Plan My24x7support.com will provide a detailed Support plan for the implementation and the cost/month to maintain custom code and Salesforce functionality. We will work in conjunction with Salesforce Premier Support to provide the support.

Project Team :

  1. Project Executive - provides high-level guidance and oversight to the project throughout engagement. The project executive will be responsible for contract negotiations and will be responsible for the entire delivery of the project.
  2. Project Manager/Sr. Business Analyst - Provides day-to-day management of the overall project plan and budget and also acts as a senior business analyst. The PM will deliver weekly status reports, conduct weekly conference calls, and coordinate all resources and tasks with the project team.
  3. Delivery Manager-Offshore - The Delivery manager offshore will be remotely based in US and managed by the Project Manager.
  4. Technical Architect - responsible for defining, architecting, and overseeing the solution as it is applied to the platform. The TA will also be remotely based in US and will be managed by the Project Manager.
  5. Senior Offshore Developer / Developer - works with the Technical Architect to develop custom user interfaces, code based business logic, and web service integrations.
  6. Website Graphic Designer- works with the Project Manager to design logos and Stylesheets for the web site.
  7. Offshore CMS Technical Lead/Sr. Developer: Responsible for website development. Will report into Project Manager.
  8. Offshore Data Specialist - works with the Technical Architect to specify, configure, and implement all ETL based integrations as well as the migration of legacy data.
  9. Offshore Quality Assurance Lead / Quality Assurance Analyst - responsible for creating test cases and executing the test scripts. They will use Mantis as QA tool for defect management and issue resolution process.
  10. Trainer- The Project Manager will perform a 2 day formal training of the system onsite before the Go live date.
  11. Project Sponsor/Executive- Provides the funding for the Project and is involved in all key decisions.
  12. Project Manager- Works with Project Executive/Project Manager on a daily basis to ensure the Project is running on time and budget.
  13. Business SME's: Business Area Experts who will define and approve Henrico Counties business processes. They will be signing off on the Project functional deliverables.

Project Management :

  1. Key to methodology is ongoing and consistent project management and consistent client interaction throughout the engagement
  2. The Project Manager
    • Coordinates, schedules, and oversees the entire project
    • Serves as the primary liaison between the client and BiznusSoft
    • Manages the change control process
    • Tracks and communicates all open items and project risks including mitigation and contingency plans
  3. Key Project Management Activities and Deliverables:
    • Create and publishes the project charter, which extends what is defined in the SOW and establishes the formal framework for the project
    • Submit project status reports communicating key milestones, budget, and overall timeline, as well as maintaining the project plan
    • Communicate items requiring management attention
    • Formally document and communicate any meaningful changes in scope requiring client approval, regardless of the impact on time and budget

Change, Issue, and Risk Management :

  1. Change Management
    • Identify and track all requested changes to the project scope and approved requirements regardless of their impact to the timeline or budget
    • Identify impact & risk and submit all changes for formal client approval
  2. Issue Management
    • Document all identified issues impacting the project and assign responsibility to consulting team or client resources for resolution
    • Communicate and track the status of all open issues as part of the project status reporting process
    • If necessary, issue review meetings based on SME's schedules
  3. Risk Management
    • Identify and track all potential risks to the projects success
    • Assesses each risk for impact and probability
    • Identify, document, and communicate mitigation and/or contingency strategies
    • Monitor and update each active risk.

Training Program :

  1. Role based User Guides would be provided.
  2. Onsite training is recommended.
  3. Upon successful completion of Training, support is provided during the User Acceptance Testing phase, which will ensure that all users are adapting to the new solution.