Professional Documents
Culture Documents
ACCELERO
Agenda
© 2022 Kaisa Consulting Company, Inc. All Rights Reserved
Ground Rules
Silence or set devices to vibrate during sessions.
Objectives met
A. Unique
B. Temporary
C. Ongoing and repetitive
D. A part of every project activity
01 02 03 04
Regulatory, Stakeholder Technological Create,
legal, or social requests advances improve, or fix
requirements products,
processes, or
services
Project Represents an agreement on and commitment to the deliverables of the project, as well as the scope, time constraints, resources and standards.
Management Plan It also aims to establish the foundation of the implementation project by defining the project management methodology, control structures, and
other important factors critical to the success of the project
Formally recognizes the start of the project. Both Project Managers of Kaisa and the Client should present a shared view of the
Project Kickoff project and ensure understanding of the Project Management Plan among stakeholders and team members. Base project elements, which
involve the client, such as the timeline, roles and responsibilities, and critical success factors, are also discussed to ensure that all members of
the project team are aligned
Refers to an undertaking which attempts to identify any process gaps and provide resolutions or workarounds, subject to the approval of the Client
Fit Gap Analysis
Documents the business process requirements of the company which are within the scope of the project. Aside from the as-is or
current process flow, this document contains significant information pertaining to the To-Be Process of the organization after the implementation of the
Business Blueprints system, including definition of process actors/owners, organizational unit assignments, master data, and document classifications, and workflow
approval strategies. The items defined in this document will serve as a guide in configuring the
system in the succeeding phase.
Functional Defines in detail the input parameters, functional logic, and the output requirements of each item in the WRICEF. This
Specifications aims to clearly and accurately provide the KAISA consultant with an understanding on the behavior of the requested customized program. This is
required before any development work can begin.
Translates the functional definition in the Functional Specifications Form into technical requirements. This form provides
Technical
how the tables, fields, and transaction codes in the application are used to develop the program. This will also serve as the formal documentation as
Specifications
future reference to possible modification and enhancement to the customized program.
Contains the set of identified possible variations in the proposed business process flow. This will be the basis for
Business Process
system integration testing and user acceptance testing prior to the final release of the system for production run. It is critical to test the most probable
Scenario Listing
scenarios that the users will consider for data entry and report generation.
Documents the enablement strategy on how to equip the users and other members of the team with necessary skills to prepare them in their roles during
Training Plan the productive run of the system. It is critical at this stage to define how the training will be done and if user evaluation will be performed and at what
extent
Documents the strategy to be applied in testing the expected functionalities which should be delivered by the system prior to production. This ensures
that the configured system and the developed programs are consistent with the processes and customized programs defined in the blueprints. The
Test Plan
acceptance criteria are also defined in this document to avoid ambiguity during the testing activities. Moreover, the Test Plan shall include a monitoring
process for passed and failed testing to track the efficiency of this phase.
Documents the step-by-step procedure that will serve as a guide in testing each business scenario. It also contains the test parameters, test data, and
Test Script
expected output.
Defines the different authorization roles with their assigned SAP transactions, and authorization objects. Combined with the user
Roles and ID, this document serves as the foundation of the system security. It is necessary that the Functional Team is familiar with the technical aspect of the
Authorizations system when drafting this document.
User Acceptance Contain the system output resulting from following the test scripts. These contain the results (Pass or Fail) for each corresponding set of
Testing (UAT) test parameters, test data, and actual system output. The results shall also provide information of the success/ defect rates and the time spent for rework
Results and retesting.
Defines the approach in migrating data from the legacy system to the SAP system. This includes the required information and
Data Migration Plan
the strategies for data cleansing as well
Enablement sessions conducted by the Kaisa consultants for each module, to be attended by trainers coming from the client organization who will in
Train-the-Trainer turn manage the knowledge transfer process to other end users
Aims to equip key users with SAP S/4 HANA knowledge on how to navigate and use the system in relation to their corresponding roles in
End User Training the business process. The End User Guides contain the step-by-step procedure on how to execute a transaction in SAP S/4 HANA
Contains the procedures during the transition period from the legacy system to the new SAP system. This will serve as a guide to the
Cutover Strategy users on how to handle transactions from the cut-off date on the legacy system and how these will be processed in the SAP system.
Technical Go Live Provides a checklist of all critical technical tasks and milestones that needed to be delivered prior to going live
Checklist
Business Go Live Provides a checklist of all critical functional tasks and milestones that needed to be delivered prior to going live
Checklist
Contains the configuration settings in the Implementation Guide (IMG) of the SAP system that were modified by KAISA
Configuration
Consultants during the course of the Project (including S/4 HANA configuration and integration). This document serves as a reference for future
Design (System
modifications and enhancements to the SAP system. This will also act as a guide during the configuration walk-through between KAISA Consultants
Documentation)
and the Functional Team
Provides a checklist of all delivered tasks and documentation to ensure that all deliverable items stated in the contract have
Project Closure
been provided by KAISA
Acceptance Refers to the acceptance document signed by both KAISA and the Client which signifies that the project has
(Handholding) been completed and turned over to the Client
Certificate
Technical Go Live
Business Blueprints Test Plan End User Training Project Closure
Project Kickoff Checklist
Business Go Live
Functional Specifications Test Script
Checklist
Contact us Follow us
www.kaisa.com info@kaisa.com