Prepare Test Cases

Implement
Requirement Gathering Phase

Vyntril Configuration Consolidated Review

Pre-QA
Email Status Update QA Testing
Feedback given to client on Completed
High Level Requirement. Unit
Requirement Gap Analysis
Project Take over Process Preparation for Functional Consultant
Client Onboarding Client Follow-up (Email) Ad Comp Overview
Feedback Email Functional
GAP
Finalization Test
Meeting Decision Refernce Client Core Team Requirement
Analysis/
(Client
Q&A
Start Requirement)
Bug Identified

Template:
Client Solution
Go to this navigation path in  Meet and Greet Quality Check
Vyntril Shared Drive  Roles and Responsibility  Advance Compensation
Share Drive>Vyntril>Program  Advance Compensation Processes Presentation to
Management>Templates>Template overview Session Client Ad comp core team
s by Modules>Advance  High level Requirement  Meeting Client
Compensation>Bonus
 Tenant Environment compensation Core Team
Access
No
Template Name:  Follow-up Email
 Actionable Items Jira Bug Tracking Process
Planning
Process Preparation for Functional  Client Follow-up Email
Consultant- Bonus

Bug logged in JIRA Yes

 User Manual
Testing Completed/QA Delivered
Client Communication Email UAT kickoff Meeting
 Internal Team Meeting sign off  Advance
 JIRA Project Setup Compensation
Assigned to a Analyst Administrator
 Review Predefined
Template Trainings
 Requirement document
filling
 Resource planning
Development Phase
UAT Sign off

Resolve the issue

No
Migration to Live
Testing Tenant

Template:
Production Clone to
Go to this navigation path in Sandbox (Final Testing
Testing Successful Vyntril Shared Drive
Share Drive>Vyntril>Program
before Go Live)
Management>Templates>Template
s by Modules>Advance
Compensation>Bonus

Yes Template Name:

Deployment Checklist
Go Live
Bug Closed

Post Go live Review Business User

Session Feedback
 Lesson Learnt
Report

Client Onboarding Meeting Planning Requirement Gathering Phase Development Phase Configuration Completed QA Testing UAT signoff

Internal Team Meeting: * will be run in parallel with planning This is the initiation of implementation process for client  The client requirement/s at this stage have been configured into QA encompasses the testing of the configuration that implements User Acceptance Testing (UAT), or testing, is the final stage of
Meet & Greet: requirements. Initially these are in the designated tenant (SandBox their designated tenant. The process or configuration is now post design phase in a client environment.
Advance compensation development or change request lifecycle
 Task-wise breakdown (developing work parcels) Requirement Gathering: or any as described in the Client Onboarding call). This will be an able to run on the system against the pre-decided parameters. The fundamental purpose of QA is to rigorously test the before go-live. Successful UAT would means configurators are
 First team to client point of contact.  Consists of resources allocation, and mobilization example of a cyclical approach . The Functional team has performed the needed testing implementation cycle against the agreed client requirements good to deploy the solution in Production environment.
 Team introduction. The Requirements gathering is the process of identifying your validating the configuration. corresponding to the project scope.
 Client onboarding call. Jira Project Board: project's exact requirements from start to finish. This process Design Phase: Actors:
QA Signoff Exit Criteria:
occurs during the project initiation phase and is amendable in Compensation Configurator (Workday Role-Client)
Roles & Responsibility:  Setting up of the Jira project board correspondence with the client requirement.  Logical buildup of the configuration in the tenant/ system Template QA can do Sign off after meeting the exit criteria. In exit criteria,
Go to this navigation path in Vyntril Shared Drive QA Team & Functional Consultant (Support Role – Vyntril)
 Team task assignment  Steps utilized to build the process in the tenant/ system the QA checks the following things:
 Who is doing What – (Roles involved e.g., (Engagement  Nominations of team members in Jira (Product Owner,  The configuration template will be designed in this phase Share Drive>Vyntril>Program
Manager, Coordinator, Functional Consultants) Coordinator, Manager) etc. Process: Management>Templates>Templates by Modules>Advance  The software should meet client requirements Template
 Team wise role intro – (Who has what roles)  Addition of timelines in Jira relevant to the configuration tasks Implementation Phase: Compensation>Bonus Go to this navigation path in Vyntril Shared Drive
 The process is cyclical and between the functional team and the Template Name: Configuration Document Bonus.  All the test cases should run/pass the execution. Share Drive>Vyntril>Program
High Level Requirements: Review Pre-defined Template: client. The requirements are added based on the GAP analysis  The system wide application of the configuration in practical  There should be no blocker/high issues present in the Management>Templates>Templates by Modules>Advance
that exists between the Current to the Ideal state. terms application. Compensation>Bonus
 Mandatory requirements related to a project.  Team document review of the template 
 At this step the brainstorming session will also be conducted Any development already done will be tested by the Template Name: UAT Signoff
 Set out for the project management/ engagement team.  Amending template in relevance to the requirement of the configurator at run time.
on the High Level Requirements. Template Name: User Acceptance Testing.
 Essential to the functional side of the project. current project
These are elastic. QA Failure:
Template
Resource Planning: Go to this navigation path in Vyntril Shared Drive Template In case of any bugs identified and UAT failure QA Team will refer
Client Tenant Access: Go to this navigation path in Vyntril Shared Drive * Finalized Configuration Document-Bonus Template will be
This is an internal process that occurs between the functional team. Share Drive>Vyntril>Program back to Development team.
Share Drive>Vyntril>Program used as Migration Document.
Management>Templates>Templates by Modules>Advance
 Access to client tenant/s as required and or needed (e.g., The planning operations run in parallel on a concurrent basis in
Management>Templates>Templates by Modules>Advance
respect to the Requirement Gathering Phase. Compensation>Bonus
SandBox, Implementation). Compensation>Bonus Template
Sorting modalities related to tenant access code, granting of access Go to this navigation path in Vyntril Shared Drive
Template Name: Client Requirement Gathering Document Bonus
rights, authentication etc. Template Name: Configuration Document Bonus. Share Drive>Vyntril>Program
What is the steps of review for each phase ( QA phase)
Management>Templates>Templates by Modules>Advance
Actionable Items Compensation>Bonus

*) Actionable Items will be recorded internally in a spreadsheet. Template Name: Test Scenarios for Adv Compensation-Bonus
*) Meeting discussion veracity will be subject to an Email
summary shared with all stakeholders involved.
Firefile tool