life time fitness qa coe proposal presentation 9th january

Life Time Fitness QA CoE Proposal Presentation

9th January 2017

LTF ObjectivesRFP OBJECTIVESOur understanding

DEFINEWhat is the scope of service

SOLUTION OVERVIEW

TRANSITIONHow will we transition

DELIVERHow will the services be delivered

MEASUREHow will we measure performance

OPTIMIZEHow will we improve

TRANSFORMHow will we transform

WHY HEXAWARE

Flexible

Sourcing

Capacity

1

Higher

Productivity

2

Greater

Effectiveness

3

Optimized

cost

4

Enhanced

Testing

Capabilities

5

Create an efficient, effective, reliable and flexible technology delivery group, Trusted by business leadership which delivers continuous value

• Automation First Approach

– Comprehensive automation inclusive of TDD/BDD, Model Based Testing, Usability, Performance and Security

– Achieve 80% regression test automation.

– Productivity improvement up to 40% for Test case design and Automation script design through iD2E

(Integrated Design to Execution).

• 35% cost savings in steady state

• Leverage near shore(Mexico) for achieving maximum time overlap

• 100% transparency throughout entire process – leveraging HexaView

• Post base-lining metrics, improve adherence of the following metrics linked to SLAs

– Defect Removal Efficiency (DRE) with Severity Dimension – Achieve a target of >99%

– Test coverage - Achieve a target of 100% across all application tracks

• Tool rationalization in conjunction with Hexaware solutions in the area of test automation, data testing,

performance, usability, continuous testing

• Setup LTF Learning Centre through Hexavarsity for training, induction and on-boarding

• Resource performance monitoring and improvement program every Sprint

Hexaware Commitments

• 9 Application tracks covering

– LTF Suite

– Boss, Scheduling & Registration

– CRM, Sharepoint, MS Dynamics, Reunify, Fore.com

– E-Commerce

– AEM

– Total Health

– Mobile Application

– Datawarehouse/Reporting

– Innovation

• Test Requirements Gathering

• Test Strategy & Planning

• Test case design & Automation script development

• Automation framework maintenance

• Defect Management

• Test Process streamlining and standardization covering processes, templates, metrics, guidelines, tools, and checklists

• QA Environment and Tools Assessment

• Functional Testing | System Testing | End to End Testing | User Acceptance testing support

• Visual Regression

• Data Conversion / Data Quality Testing

• Compliance Testing

• Security Testing

• Performance Testing

• Security and Compliance Testing

• Application development, new enhancements & Maintenance

• Test Environment Configuration and provisioning.

In Scope Out of Scope

Application Landscape Test Activities Test Types Out of Scope

Scope of servicesRFP OBJECTIVESOur understanding


SOLUTION OVERVIEW






WHY HEXAWARE

SOLUTION OVERVIEW

RFP OBJECTIVESOur understanding


SOLUTION OVERVIEW






WHY HEXAWARE

6

• Agile approach to transition

• Sprint 0 assessment & QA CoE model refinement

• Minimal business disruption – wave based approach

• Role based transition covering vendor and in-house FTEs

• Governance - Hexaview

• Real-time Automated metrics

• Multi tiered governance structure with Dedicated engagement manager at onsite

• SLA driven services delivery

• Continuous improvement in performance and Agile maturity

• Test Design Automation

• Early adoption of BDD

• Automation coverage for regression - 80%

• ETL Automation - DT Compress

• Performance -HexaJAWS

• Usability – UMI & Think Aloud Testing

• Security - DAST and Penetration Testing

• Service Virtualization -Pilot

• Continuous Testing in DevOps, BDD -Continuous Assurance Platform (CAP)

• LTF custom connectors for iD2E

• Performance Engineering - APM

• Implement Service Virtualization

• Crowd Testing

• PTAP – Predictive Test Analytics Platform

• Operating - all types of testing

• Shared & Support Services

• Onsite (US)-Nearshore (Mexico)-offshore (Chennai) distributed agile based delivery

• Complement Hexaware Testing solutions with LTF solutions

• SDETs - cross skillingand up skilling

Seamless Transition

Metrics Driven Governance

Improved Quality, Time to Market & User Experience

TransformationOptimized service

delivery

Key Solution Tenets

Transition



SOLUTION OVERVIEW






WHY HEXAWARE

8

Key Tenets / Transition Principles

Manage Transition as a Project

• Dedicated Transition Manager & Team with clear KRAs

• Quality gates at every milestone

• Sprint approach to Transition – 3 Sprints covering Knowledge Transfer, Shadow Phase and Reverse Shadow for 8 application tracks

Minimize Business disruption

• Parallel wave based transition approach

– Wave 1 & Wave 2 immediately move into steady state and continue with BAU activities

– Optimal use of your SME time

– Leverage existing knowledge of LTF IT & business landscape – across Total Health and Datawarehousing/Reporting application tracks.

– AS-IS transition with 15% buffer via additional resources during transition to mitigate productivity loss and cover up for unexpected early relieving of LTF employees

Train the Trainer Model customized for Agile projects

• Dedicated Vendor to Vendor transition team in India to obtain knowledge transition from LTF’s existing offshore partner based out of Belarus. The team is planned to be stationed in Chennai, India to have maximum time zone coverage during transition.

Plan Inbuilt Insurance Policy

• Frequent review of velocity and quality of deliverables

• Catch early Fix early approach

9

Transition Model

Sprint 1 (Shadow) Sprint 2 (Reverse Shadow) Sprint 3 (Complete Ownership)

Wave 2

Wave 1

LTF SuiteScheduling & RegAEMTotal Health Mobile Applications

CRME Commerce

Data warehousing

2 WeeksWeek-1 Week-2 Week-3 Week-5 Week-7 Week-9Week-8Week-4 Week-6

Sprint 0 ( Pre - Transition)

Medium and Simple Applications

Complex Applications

Successful pilot signoffSigned off Transition plan

Signed off Application wise KT document & Learnings from Sprint 1

Shadow phase sign off

Reverse Shadow phase sign off

Metrics Baselining

% Completion by App Streams

% Completion by Waves DREAutomation & Test

Coverage

Qu

ality Gate

1

Qu

ality Gate

2 2

2

Qu

ality Gate

3

Qu

ality Gate

4

10

Attached Excel sheet provides more details on the transition

roles & responsibilities

for all stakeholders

During Pre Transition Phase

• Ensure availability of all key stakeholders and necessary environment access as required for assessment.

• One on one sessions to ensure, understanding of environment, impact of the transition and details on upcoming release plans and commitments made to business

• Transition project plan finalization

In Vendor to Vendor Transition

• Life Time Fitness to enable and lead communication plans on transition with existing offshore Vendor

• LTF to closely monitor transition progress and act as escalation team for any issue with vendor during transition

• LTF to schedule transition sessions with existing offshore vendor and ensure complete cooperation from them

• Be available and cooperate for all KT sessions – Share knowledge till clear understanding of the technical environment and processes

• Existing offshore vendor to Provide functional, technical and process documentation to transition team

• LTF to review of KT documents/ handbooks prepared by Hexaware Team

Support Required from Life Time Fitness during Transition

11

Deliver



SOLUTION OVERVIEW






WHY HEXAWARE

12

Current Operating Model

LTF suite

BOSS/Scheduling/Registration

CRM, Share Point, AEM

E Commerce

Mobile Apps Innovation

Total Health

DW/Reporting

Bu

sin

ess

U

sers

Serv

ice

R

eq

ue

st

Web Alerts

Email

Call

Mobile Application Testing & Automation script development using LTAC

Vendor team

Test Process

Application Directors

Scrum Teams

LTF IT Head

LTF FTEs’ + Contractors (supporting different scrum teams across Functional & Non functional testing for non mobile applications)

QA CoE

Leads

13

Target Operating Model (TOM)

LTF suite

BOSS/Scheduling/Registration

CRM, Share Point, AEM E commerce Mobile Apps InnovationTotal Health D/w reporting

Performance, Security, Usability, Accessibility

Application Directors

Test Automation – Automation framework development, maintenance and implementation Shared Services

Governance support

Scrum Teams

LTF QA CoE Director Hexaware Engagement ManagerDemand Planning & fulfillment, Test Strategy & Planning , Metrics & Reporting

SDETs (multi-skilled team members supporting different scrum teams – manual testing and automation)

Test Data Mgmt. Test Environment Mgmt. Test Process Test Tools Shared supportservices

HEXAVIEW

Tools Tools Administration

iD2E TDM HEXAJAWS DT compress

Hexaware in house tools & accelerators

CAP

Knowledge Mgt

On demand skill based ramp up based on 3 month rolling forecast

SDETs aligned to scrum teams

Leads

Bu

sin

ess

U

sers

Serv

ice

R

eq

ue

st

Web Alerts

Email

Call

LTF IT Head

14

Platform Stream

Our understanding of application functionality

Target End Users

Technology Types of Testing Skills SetKey Roles required

LTF Suite All internal LTF Applications (MMS, Product Configurator etc.) and My LT site

LTF Employees & Members

Java, SQL Manual Functional Testing, Database testing, Test Automation

SDET with DB testing, Java scriptingQA Lead with test process Exp

QA LeadSDET

BOSS -Scheduling & Registration

Scheduling and registration application to support all LTF events

LTF Employees Delphi, .NET, Linux, SQL

Database testing, Manual Functional Testing and Test Automation

SDET with exposure to Linux SDET

CRM MS Dynamics and SFDC for CRM. Used by LTF sales teams

LTF Employees Salesforce, MSDynamics

Manual functional testing, Test Automation

SDET with test automation and functional Exp on SalesforceQA Lead with test process Exp

SDETQA Lead

Ecommerce Hybris is the E Commerce platform

LTF Members Java, Linux, SQL

Manual functional testing, Database Testing, Test Automation, Security testing, Usability (Visual QA, think aloud) & accessibility testing, Performance Testing

SDET with Web testing and web based automation experiencePerformance testers with Jmeter tool experience

SDETQA LeadSecurity & Performance

AEM AEM is their content management engine

LTF Employees & Members

Adobe AEM Manual Functional Testing,Cross Browser, Test Automation, Security testing, Usability (Visual QA, think aloud) & accessibility testing, Performance Testing

SDET with CMS testing experience andQA lead

SDETQA Lead, Security & Performance

Application track wise QA details

15

Application track wise QA details

Platform Stream

Our understanding of application functionality

Target End Users

Technology Types of Testing Skills SetKey Roles required

Total Health Application related to wellness business unit like Coaching Platform, challenge engine, My Plan etc.

LTF Members .NET, HTML5, SQL

Manual functional testing, Database Testing, Test Automation, Security testing, Usability (Visual QA, think aloud) & accessibility testing, Performance Testing

SDET with Web testing and web based automation experienceSecurity testers with experience in web security testingPerformance testers experience in Jmeter and other web based performance test tools.

SDETQA LeadSecurity & Performance Tester

Mobile Application

Native mobile Applications for iOS and Android built on Xamarin (LT Health, LT Group Fitness, Member Advantage, LT Athletic Events, Life Yoga, Experience Life Magazine & LT Connect)

LTF Customers Xamarin Manual Functional, Security testing, cross browser/browser compatibility testing, Usability & accessibility testing, Performance testing, test automation

SDET with mobile and automation testing using tools like Xamarin, SeeTest, Perfecto, Appium

SDET, Security & Performance

Data warehouse/ Reporting

Informatica for ETL and Cognos for reporting

LTF Employees Informatica, Cognos

DW/ETL testing (Data conversion/Data Quality testing), BI reports testing, Automation

ETL Testers with automation skills SDET

16

Service Delivery: Integrated and Cohesive Tools

17

Automation First Architecture for LTF

Automated Code Review

Code QualityAssurance

Continuous Testing in DevOps

Automated Test design – Test execution –Test reporting

Automation Framework / Accelerator

(LTAC/QTA/STM))

Automated Test Scripts

Automation

Automated TestExecution

Connectors/ Publisher

Functional Spec / User

Stories/ BDD Feature Files

Automated Test Design

Test Management Tool (JIRA/Zephyr.)

1. New test cases for progression

2. Modification to impacted regression test cases

Fun

ctio

nal

Manual

Conformiq

Updated Model Repository

Automated Documentation

of Test Cases

Hexaview

Predictive Test Analytics

Platform (PTAP)

Risk-Based Testing

Non-Functional(HexaJAWS)

2

1

56

7

8

34

SV (Service V)

TDM(Gen Rocket)

Continuous Assurance Platform

– Use Cases

EY Atlas requirement modelled.docx

EY_iD2E_Selenium.mp4

http://115.69.83.212:8080/Insight360Demo/home.html

Pinboard Functionalities_Phase1_V4.xls

CAP_UseCases.xlsx

EY_MBT_Edited With Callout_V3_Agile Req.mp4

18

BDD and Test Automation Process Model

Given When Then Gherkin

Features

Application and Test Automation Step Definitions

Developer

Business Analysts, QA, Dev and End Users writing the use cases and stories

Application Code

Automation Object Query and Assertions

Automation Results

Cross Platform App

Build Results

FEEDBACK on the build and automation results

SDET

COLLABORATION

BA

End User

19

Suggested Test Automation Workflow in Jira

20

Usability Testing

Usability testing evaluates an application’s ‘ease of use’ from an end user perspective andprovides actionable insights for optimizing user efforts intuitively learn and use the application.

Our comprehensive approach to Usability testing offers four holistic methods that ensure aproduct meet expectations and delight its users.

21

Steady State Proposed LTF Learning Center

LTF

Learning

Center

22

Proactive Consultant Performance Management

3 months

• Invalid defects, defect leaks to UAT/Production for respective user stories

• Productivity

• Ability to multitask

• Collaboration skills

Performance Measurement Parameters

23

Governance, metrics & reporting



SOLUTION OVERVIEW






WHY HEXAWARE

24

Governance & Review

Strategy

• Performance Management• Security Management• Service Management• Story Elaboration• Product Backlog Management

• Set Engagement Directives• Plan Budget & Investments• Future Goal Alignment

• Relationship Management• Engagement Reporting• Customer Happiness• Project Health Index• Escalation Management• Leverage of Hexaware Labs &

Tools

Measure Success of the Relationship

TacticalMeasure Service

Level Commitments

Life Time Fitness Hexaware

Level I

Level II

• Delivery Management• Financial Management• Security Management• Performance Feedback

• Milestones• SLA Performance• Customer Satisfaction• Resource Management• Competency Management• Communication• Client Value Adds

Operational

Improvement Measures

Level III

• Delivery Management• Velocity• Earned Business Value

• Story Elaboration• Project Deliverables• Issue Resolution

DeliveryLevel IV

Micheal Burgess – CDONic Mulkey – VP, Technology

Janice Bethke – Director QA & Process

LTT Application Group Directors

Application Group Scrum Teams

Milan BhattHealthcare and Insurance Business

Head

Nagendra BSDelivery Leader

Neil FoxService

Improvement Lead

Hexaware Application Group Scrum Teams

Quarterly

Release Meetings / Demos

Monthly/Bi-weekly

Weekly /Bi-weekly

Scrum of Scrums

Daily

Per Sprint

Standup

• Set Engagement Directives• Plan Budget & Investments• Future Goal Alignment

Planning; Demo / Review / Retrospective; Backlog grooming

25

Single source of objective truth

• Integration with JIRA, ALM, QC

• Set targets and thresholds for key metrics, alerts sent when thresholds are not met

• Role based view, e-mailing feature, archiving daily / weekly reports for audit

• Data collected twice a day with ability to do on-demand refresh

• Ability to drill down from business line to a defect in a project

• Reports generated

Active project dashboard

Daily status report

Weekly status report

Release quality analysis

Trend analysis

• Data available for all stakeholders

Business line / Sub Business line status

Active projects status

Individual release status

26

Hexaview – Snapshots

Business line / Sub Business line status

Active projects status

Individual release status

27

Hexaview – Daily Status Graphs

28

Insight Hexaview – Weekly Progress Graphs

29

Hexaview – Release Quality Analysis

30

Metrics

Quality Metrics

Defect Rejection Ratio Test Case Execution %

Defect Removal Efficiency (Performance Score) Initial Pass rate

Defect Leakage to UAT Requirement Execution %

Defect By Status Defect Ageing Heat map

Defect By Severity Classification of UAT defects

Defects by Root Cause Unit Test Candidates

Defects by Modules Component / Module wise execution % / defects

Defect Severity Index Pass / Fail / Retest %

31

Optimize

KEY LEVERS

KPIs

Agile

Data

Automation

Tools

User Experience

HexaView Dashboard

Improve Agile maturityCollaborative and empowered teamsImplement TDD / BDD

ETL automationTest data automation

Test design automationIncrease regression automationspecifically for mobile

Tool evangelization

Usability, performance& security testing



SOLUTION OVERVIEW






WHY HEXAWARE

32

Transform



SOLUTION OVERVIEW






WHY HEXAWARE

33

Key Transformation Levers

• Consolidation and standardization of Tool set for Test Management, Automation, Performance and Security testing

• Usage of Hexaware third party alliance solutions where ever relevant for higher efficiencies.

4

Tools Optimization

• End to end automation across test lifecycle – starting from design to reporting.

• Higher efficiencies through connectors between design & execution – ~40% improvements in productivity

1

iD2E – Lifecycle Automation

• Implementation of Continuous Assurance Platform

• Leverage iD2E for BDD automation2

Continuous Testing – as part of Devops & BDD

• Predictive Test Analytics platform (PTAP)• Integration of PTAP with Hexaview6

Test Analytics

• Improved Multichannel and omnichannel experience through– IoT testing involving wearable's– Crowd testing and usability testing for improved end

user experience

3

Digital readiness

• Parallel development and testing• Overcome dependencies on environment , data

and third party systems• SV test framework

5

Service Virtualization

• Predictability/Reliability

• Cost• Quality• Speed

34

WHY HEXAWARE



SOLUTION OVERVIEW






WHY HEXAWARE

35

Our Readiness

STATUS

Account Leadership Team

Governance Dashboard

Transition Team

Full Team

Transition Toolkit

Transformation Blue print

Customer Advocacy Team

Account Manager, QA Engagement Manager, Transition Manager, Account Service Delivery Manager, Operations Manager

Metrics driven governance

Integrated transition task force

QA Leads, QA Analyst, Automation Lead, SDETs, Automation Leads, Performance Architect & Security Tester

Transition Plan template, strategy, Transition SME Handover Checklist, Knowledge Acquisition Document, Guidelines for Knowledge Transition & Steady State Awareness Checklist

Road Map and Plan for Continuous ImprovementDeepak Jayavant, Neil Fox, Darshan Dave

Current = 70%During Transition : 100%

100%

100%

Will be on Target

100%

ELEMENTS

Current = 70%In 4 Weeks = 100%

100%

36

Why Hexaware

Executive Management Commitment

15% investment in Year 1 to neutralize

productivity loss

150,000 $ investment in

transition

Automation First Approach for Testing

Risk Mitigation through nearshore

operating model

Vendor to Vendor Transition Experience

Investment of a dedicated Agile

coach for LTF

Our deep understanding on LTF's Application

Landscape

Understanding of LTF’s culture

Guaranteed savings of 35%

Hexaware is the most flexible partner to work with in the

industry

37© Hexaware Technologies. All rights reserved. | www.hexaware.com

Partnership Reimagined

38

Appendix

39

Agile Model – One Service Provide Vs Different Providers for Dev & QAS.

No.

Key Parameters in Agile

deliverySame service provider for Dev and QA Dev and QA - Different Service providers

1"One Team" - focus on

common goal

Greater collaboration and team work between

dev and QA to achieve common goals for each

sprint – provides an environment for true multi-

functional skills to be leveraged (SDETs)

Tough to align - Most often the responsibility of aligning the dev

and QA teams to a common goal for the scrum team, is taken up

by the client’s product owner

2 Collaboration Very High

Each service provider focusses more on their respective scope of

work leading to higher conflicts and escalations which the client

may end up resolving

3 Transparency

Issues that may impact velocity of the scrum

team get bubbled up promptly. Transparency

on sprint metrics after every sprint. Use of the

same tool for progress and metrics reporting is

common

Tendency to focus more on reporting the respective Dev and QA

metrics rather than overall sprint metrics. Most of the times service

providers try and influence their respective tools for Dev and QA

unless there is a client specified common tool

4Accountability and

ownershipFull accountability and ownership

Since the responsibility for Dev and QA is split, there is a tendency

for finger pointing when sprint targets are not met during

retrospectives

5 Automation and skills

Greater push for automation across dev and QA

with SDETs having the ability to switch tasks

and drive higher automation

QA teams tend to focus more on test process, quality gates,

documentation rather than automation

6 Productivity

Closer collaboration – dev supports QA and QA

pitches in for speeding up dev (unit tests, build

deployments) when needed leading to higher

productivity. Lends itself better to implement

BDD

The productivity does become a function of the relationship

between the Dev and QA teams

7 Quality of Delivery Easier to implement "Speed with Quality"

Dev teams focus on speed and usually depend on QA to be the

guardians of quality (eg not enough unit testing, reopened

defects).

Our recommendation - Single service provider for Dev and QA for agile delivery

40

App Dev and QA Synergies with One Vendor

• Avoid redundant application knowledge transition & save SME time

• Avoid resistance and ramp-up time on vendor accelerators and tools

• Increased transparency and more collaborative vs competitive environment

• Delivery performance reporting is easier with single vendor

• Resource ramp up from Flexi teams quicker with common knowledge management

• Defect turn around time improved with less escalations & more accountability

• Both teams have a stake in vendor SLA performance

• Less intervention and mediation by customer between vendors

• High performing teams following one Agile methodology under the HPE framework from Hexaware’s Agile coach

• Better alignment, common approach and increased adoption rate to customer’s future direction (BDD)

Our understanding of current testing landscapeRFP OBJECTIVESOur understanding


SOLUTION OVERVIEW






PROOF POINTSWhere have we done it before

Testing Organization:

•Currently a centralized function around Quality Assurance and Testing.

•Process standardization has been achieved to a great extent with a dedicated team.

•Part of the testing is being managed by contracted vendor team from Russia

Application Landscape:

•9 application tracks with a total team of 56 developers.

Testing Tools

•Currently, JIRA is used for agile project management.

•Agile boards are used to help plan, track and manage all of the agile software development projects and to provide reports and metrics.

Testing Environments

•At present there are mainly 3 environments for QA - QA, Stage and Production

•The main environment for Testing is the QA Environment

•QA is a shared environment with developers and business members

Testing Process

•Software development methodology

•Agile methodology to improve predictability through incremental, iterative work cadences and empirical feedback with Scrum as a framework.

•Sprint planning meetings are conducted to determine the work to be completed by the team in the next sprint from the backlog which is the center of the sprint planning meeting,

•Sprint planning meetings are used to estimate stories, adjust sprint scope, check velocity, and re-prioritize issues in real-time.

•Scrum boards are used to visualize the work in a given sprint to include all stories, tasks and sub-tasks that the agile teams need to perform for the sprint.

Test Process - Reporting:

•Life Time Fitness Test Automation Center" (LTAC) report per project

•PowerMapper > SortSite Link Checking Report, Sortsite Accessibility Report

•Zephyr Manual Test Report

Test Process - Metrics: JIRA is currently used to capture the following metrics

•Test Case Coverage % by automated vs manual

•Test Case Tier by automated vs manual

•Test Cases by component

•Defects open by browsers/device

•Defects open by component


Transition Rationale – Application Defect Density

• Application stability index - a key indicator for application wave categorization derived from No of

stories/sprint and avg defects/story data provided.

High Stability

Low Stability

Medium

Stability

# Application NameDefects

per story

Application

Defect

density

1 LTF Suite 1

2 Boss, Scheduling & Registration 2.8

4

CRM - Sharepoint,

MS Dynamics, Reunify

& force.com

0.5

5 E-Commerce 1

6 AEM 2

7 Total Health 1.8

8 Mobile Application 3.56

9 Datawarehouse/Reporting 0.1

• Defects/story <=1 –

Applications are more stable

• Defects/story >1 and <2 –

Applications may be require a

little more QA focus

• Defects/story>2 – Applications

require high QA focus


Transition Rationale – Application knowledge & Business Criticality

• Hexaware has worked in 2 of the Application tracks and outside of that as an Organization, we have

experience in working with other application areas too. Hexaware has a dedicated practice for Mobility with

extensive experience in Mobile Testing.

• Also, based on our experience in working with LTF in the past, we have also arrived at our understanding of

the business criticality of these application tracks which has been used to derive the business criticality

High Business

criticalityNo knowledge

Medium

business

criticality

Medium

Knoweldge

High knowledge

# Application NameBusiness

Criticality

Our knowledge

on the

applications

1 LTF Suite

2 Boss, Scheduling & Registration

3

CRM - Sharepoint,

MS Dynamics, Reunify

& force.com

4 E-Commerce

5 AEM

6 Total Health

7 Mobile Application

8 Datawarehouse/Reporting

• Applications with higher

business criticality will be

prioritized

• Applications where Hexaware

has working knowledge will

require reduced transition

effort.


Transition wave grouping & other key considerations

• Assessment of LTF current landscape

• Application Stability & Complexity

• Business Criticality Projects & Impact

• Production Defects, Tickets & Incident

Rate

• QA CoE Project Pilot and Sign off.

• Transition Plan finalization - across

the 8 application tracks

• Stakeholders Availability (Location,

FTE vs Vendor)

• Role & Responsibility Impact (QA

Leads /Rebadge/Role Change)

• Tools & Environment Access &

Connectivity

Pre-Transition (Sprint 0: Wk-1,

Wk-2)

Wave 1

Critical Apps

Shadow

Reverse

Shadow

Fully Functional &

Execution

Ownership

Wave 2

Non-Critical

Apps

Metrics

• Onsite – 5

• Rebadged - 2

• Near Shore – 0

• Offshore – 4

TOTAL - 16

• Onsite – 4

• Rebadged - 1

• Near Shore – 0

• Offshore – 8

TOTAL - 13

Wave 1 Wave 2 Wave 3

Feb 2 – Feb 23 Feb 24 – Mar 15 Mar 16 – Apr 6

% Completion by App Streams

% Completion by Waves

Sprint 3Sprint 2Sprint 1Release Planning

Sprint 3Sprint 2Sprint 1

WAVE 1 APPS

CRM

LTF Suite

E-Commerce

Total Health

AEM

WAVE 2 APPS

Boss, Scheduling &

Registration

Mobile Applications

Datawarehouse Testing

Qu

ality

Ga

te

1 • Successful pilot

signoff

• Signed off

Transition plan

Qu

ality

Ga

te

2

Qu

ality

Ga

te

3

Qu

ality

Ga

te

1

• Signed off

Application

wise KT

document

• Shadow

phase sign

off

• Reverse

Shadow

phase sign

off

• Move to

steady state Steady State Activities:

• Groom User Stories

• Plan & Deliver User Stories through

HPE framework

• Demos

• Metrics & Reporting


Transition Resource Rationale

• Application QA Productivity = Current QA team member count/Avg no of stories delivered per sprint

Application

Productivity

Category

<=5 Complex

6 to 10 Medium

>10 Simple

QA Lead 1 LTF Suite BOSS

QA Lead 2 CRM AEM

QA Lead 3 Ecommerce Total Health

QA Lead 4 Data

warehousing & Reporting

Mobile Application

• More resources (SDETs - Software development Engineers in Testing) for Applications with higher manual test cases

• All Customer Facing applications (ecommerce, Total Health, Mobile Application) will include an element of performance and security testing.

Hence Performance & Security testing engineers are included as part of the transition

• Dedicated QA Leads for Applications of higher complexity

• Automation focus during transition is to understand automation scripts for respective application tracks

• Onsite transition resources will take 1 on 1 transition from existing QA leads by matching head to head to maximize knowledge transition

• Offshore India resource to work with vendor resources in Russia during their time zone to increase productivity and communication


Daily Stand-up meeting End of Day review End of Week Review

Daily Meetings are good for initial planning, Later; these can be

incorporated into an “as-required” or merged into the Weekly

Meeting schedule. Service Line Leaders from the Hexaware

transition team, representatives from the Hexaware and Life

Time Fitness Transition Manager will participate.

The following agenda will be adopted:

Track Leaders meet with their respective

teams and adopt the following agenda:

Service Line Leaders from the Hexaware transition team,

representatives from Life Time Fitness and Hexaware will

participate.

The following agenda will be adopted

List deviations relating to interdependencies

Identify underlying issues to get buy-in from other track

teams (prioritization of issues will be moderated by the

Transition Manager)

Life Time Fitness Transition Manager will take

responsibility for coordination with Life Time Fitness

internal teams and third-party as appropriate for

addressing issues outside

Identify actionable items and responsibility

Update the issue register

Review plan for the day

Review progress for the day

Identify deviations and underlying

issues

Record issues related to

interdependencies with other teams

Define plan for next day

Review status of deliverables and sign-off status

Review risks to the transition plan

Review unresolved issues by priority and age


Update the issue / risk registers

Review possibility of resource reallocation required to

meet plan

Review overall plan, and revise plan (if required, and as

approved by Transition Manager)

In addition to the above, we will have a fortnightly review conducted by the governance team to identify any directional changes to the transition plan. This meeting will

also be used to obtain any changes in the LTF organization priorities that may have an impact on the Transition Plan. Status Report will be prepared by the Transition

Manager for this review that will provide reports on progress in each track, open issues, and transition deliverables.

Transition Cadence & Participants


Transition Risks & Mitigation PlanType of

RiskRisk Description Mitigation Plan

Resource Risks

• Inadequate involvement of key stakeholders from LTF, existing Vendor and new partner to lead the transition process.

• Non Identification of right resources for transition from vendor

• Non Retention of key resources after transition

• LTF to identify key resources and ensure complete cooperation from existing vendor to ensure smooth transition

• LTF and Hexaware to cohesively select the key stakeholders to lead the transition process

• Retain the right resources as a part of the core team

Operational Risks

• Unavailability of key SME’s from LTF and existing vendor

• Ineffective knowledge transfer due to lack of interest in providing KT

• Improper KAD

• Gamify- Identify and incentivize all key core members providing KT.• Overlap offshore hours with onsite hours at least for ½ day to increase

effectiveness of KT. For Europe (Vendor) it could be longer.• Online Conference sessions for facilitate transition.• Diligently follow acceptance and sign off criteria at the end of every

week and phase

Timeline Risk

• Ineffective KT leads to extended timelines

• Key business initiatives which supersedes the transition plan and timelines

• Network Connectivity and access issues for offshore resources

• Prepare & budget for additional KT. However, set an internal target 2 weeks ahead of planned KT completion date.

• Recommend that no major transformation initiatives go live during this critical phase.

• Start early and utilize pre transition phase diligently• Prepare detailed transition plan with clear RACI matrix


Transition Risks & Mitigation Plan

Type of Risk Risk Description Mitigation Plan

Cultural Risk

• Understanding India, Mexico work ethic norms.• Lack of clear and transparent communication• Increased re-work• Slower response times

• Overlap hours with US for the all team members for the first six months followed by select team on rotation model• For LTF, as this is a first time to work with India based & Mexico based teams we will set up transition workshops.• Measure Do/Say Ratios on each side to improve commit integrity factor• A clear communication plan and schedule to be agreed from the beginning.

Control Risk

• Lack of proper governance• Lack of daily oversight• Improper reporting• Missing timelines of key activities

• A detailed transition plan getting to specific of what would be accomplished each day of a week.• A Bi-Weekly Steering Committee Meeting to ensure governance• Clear scope and defined stage gates• An escalation mechanism to identify & deal with risks

Financial Risk

• Longer Transition than Required• Increased usage of LTF teams• Increased travel & expense budget• Delay in savings

· Hexaware to underwrite savings for LTF.


Sl. No. Transition Asset Name Template

1. Transition Plan template and strategy

2. Transition SME Handover Checklist

3. Knowledge Acquisition Document

4. Transition Process Overview

5. Guidelines for Knowledge Transition

6. Steady State Awareness Checklist

Hexaware Transition Tool Kit – Sample Templates

The Transition tool kit documents and templates will be reviewed with LTF and necessary changes will be made


Name of Client -Leading life sciences data provider

Details

Number of locations involved in Transition

4 - US, UK, India – 2 locations

Number of Vendors involved 2

Client and Vendor Team Size Leading Lifesciences data provider62

Hexaware Transition Team Size 47

Hexaware Transition Resource Split across locations

UK – 4US – 3India – 40

Transition Duration 4 – 12 months. Depending on the complexity of the applications and SME availability

Challenges during Transition SME availabilityCurrent project and BAU commitments for SME’sBusiness PrioritizationSME / transition team attritionNetwork connectivitySME knowledge on applicationsSPOC for transitionOverall completeness of KT for application. SME’s sometimes keep information.

How did we overcome Dedicated transition manager and SPOC from client and vendor.Involvement from stakeholders to firm up SME commitmentBack up SME’s and transition teamsCollecting historical data and documents relating to the application and storing in central repositoryNo documents / data in local computersCommunication and discussion with business on BAU supportDedicated link between the organizations part of the transitionDetail transition plan covering each and every area within the application.

Multi Location, Vendor to Vendor Transition Case Study


Name of Client : Leading Private bank in the US

Details


US , India

Number of Vendors involved 5 Vendor

Client and Vendor Team Size Overall size 150 ( 5 Vendor)

Hexaware Transition Team Size 30


US – 5 , Singapore – 2 , India 23

Transition Duration Phase wise Transition ( took 9 months for complete transition )

Challenges during Transition Non availability of documentation ( KAD) No – availability of Vendor key team Getting time from Business and IT consultantGetting application access on time

How did we overcome Preparation of knowledge acquisition document Validation through reverse KT Robust Transition Metrics and Status reporting Involvement of Business Analyst during Transition

Multi Location, Multi Vendors Transition Case Study


Multi Location Vendor to Vendor Transition Case Study

Name of Client – Leading

Telecom provider in Europe

Details

Number of locations involved

in Transition

Netherlands India

Number of Vendors involved 1

Client and Vendor Team Size Overall team size 100

Hexaware Transition Team

Size

10

Hexaware Transition Resource

Split across locations

3 – Onsite 7- Hexaware

Transition Duration 3 months

Challenges during Transition Lack of documentation

Customer was also involved with transitioning internal IT to Agile

How did we overcome Prepared detailed documentation as part of transition

Reverse KT to validate the documentation and understanding

Sign off on the KAD delivered as part of KT

Transition team was coached in Agile and took up CSM certifications


Vendor to Vendor Transition Case Study

Name of Client – One of the largest Life science company in US

Details – Transition of MIS Applications involving QA, SFDC, SAP, PeopleSoft & Time keeping systems


Chennai, IndiaPlymouth Meeting, PA, US

Number of Vendors involved One

Client and Vendor Team Size Client team size – 35 consultantsVendor Team size – 15 consultants

Hexaware Transition Team Size

15 consultants


US – 4Chennai, India - 11

Transition Duration 2 Months

Challenges during Transition Early exit of vendor consultants Insufficient documentation of existing applications Absence of SME’s from vendor side for providing final signoff

How did we overcome Managed the situation with additional buffers planned initially Usage of tools to reengineer application and reverse engineer to get system knowledge Worked with client and identified client representatives for providing signoff


Sl No Role Skills Responsibilities

1 Transition &LTF CoE Manager

• Minimum 15 yrs. experience in Test management roles and transition experience• Formulation and implementation of Software Testing strategies• Resource management (allocation, monitoring, motivating etc.)• Preparation/review of test plans, Test reports• Training and Mentoring• Manage and resolve escalations• Risk management and mitigation plans

• Transition & QCoE Manager responsible for end to end LTF QA CoE engagement• Responsible for Transition of all 8 Application tracks from the incumbent vendor

and LTF QA FTEs to Hexaware.• Post transition, delivery of all test services as part of QA CoE in the Steady state.• Works closely with LTF QA CoE Manager for TCoE Governance activities. • Assists LTF QA CoE Manager with Test Management activities for all 8 application

tracks. Managing the near shore team for test execution and coordination between US, near shore & India teams.

• Program/Project risk & issue resolution

2 SDET (Software Development Engineers in Testing)

• Minimum 3 to 5 years with multiple test tools, QA functional testing process & scripting languages

• Implement and develop automated test practices for web and service based applications primarily using LTAC framework on top of selenium.

• Design and create test scripts using C# and/or java to address areas such as database impacts, software scenarios, regression testing, negative testing, error or bug retests, or usability in preparation for implementation.

• Perform functional, accessibility and Web services testing across applications• Work with the QA Manager and colleagues to define process and strategy

associated with automation. • Identify, analyze, and document problems with program function, output, online

screen, or content. • Plan test schedules or strategies in accordance with project scope/delivery dates. • Participate in product design reviews to provide input on functional

requirements, product designs, schedules, or potential problems.

• Implement and develop automated test practices for web and service based applications primarily using LTAC framework on top of selenium.

• Design and create test scripts using C# and/or java to address areas such as database impacts, software scenarios, regression testing, negative testing, error or bug retests, or usability in preparation for implementation.

• Perform functional, accessibility and Web services testing across applications• Work with the QA Manager and colleagues to define process and strategy

associated with automation. • Identify, analyze, and document problems with program function, output, online

screen, or content. • Plan test schedules or strategies in accordance with project scope/delivery dates. • Participate in product design reviews to provide input on functional requirements,

product designs, schedules, or potential problems

Key Roles & Skill Description


Sl No Role Skills Responsibilities

3 QA Lead • More than 7 years of testing and quality assurance experience in a variety of

industries and specializations.

• Specializations include Functional testing, BI testing, Web service testing,

ETL Testing, Unified messaging and User acceptance testing.

• Knowledge of test processes and understanding of test metrics.

• Experienced in End-to-end testing in terms of preparing test strategy, test

plan, understanding and securing test environments and data, in various

phases of the project lifecycle including System Testing and User

Acceptance Testing.

• Recognizes issues (e.g. with requirements, design, implementation, etc.) and

works with appropriate resources to address and resolve

• Ability to work under deadlines and perform multiple tasks effectively and

concurrently

• Knowledge in CMM Level process, coordinated for SQA audits, enforce all

processes for testing as per standards defined by the organization

• Experience on Defect management process and conducting Triage calls.

• Responsible for QA activities for identified application tracks

• Participate in status review meeting with LTF QA Manager, LTF Location Managers

and development team manager

• Coordinates activities between US, nearshore and offshore QA teams.

• Participate in Root Cause analysis.

• Coordination of handoffs at various points.

• Review estimates and manage test teams

• Manage Application related escalations and works out resolutions

• Plan & prioritize testing activities on a day to day basis

• Monitor progress and proactively inform risks to the US counterpart

• Review of Weekly Status reports and QA deliverables

• Ensure high quality and timely delivery of deliverables

4 Automation

Architect

• 9+ years of experience in Automation Testing and Database Testing.

• Expertise in Functional, regression testing and test automation consulting.

• Strong knowledge in requirements understanding and test planning.

• Well versed in implementing various automation frameworks with respect to

different technologies, development models (including Agile) and domains

• Experienced in preparing automation plan, automation strategy and leading

projects to be on track with the project plan and within approved budget

• Experienced in managing and leading a team with varied skill sets to achieve

the desired quality objectives

• Expertise in automation tools such as QTP, SilkTest, TestComplete, QTA

and MS CodedUI

• Conduct assessment of existing automation framework - LTAC and define roadmap

for improvement.

• Identify potential automation candidates and develop automation strategies.

• Provide guidance to n Sprint automation issues and also help develop application

specific automation solutions.

• New technology advocacy and adoption

• Provides automation script development guidance to SDET teams.

• Point of contact for Technical issues

• Reviews Automation process and Scripts/Libraries

Key Roles & Skill Description


Client : Leading life sciences data provider Year 1 Year 2 Year 3

Overall Team Size 42 40 37

% Onsite (Specify Locations) 30 22 20

% Offshore (Chennai, India) 68 78 80

% Nearshore (Mexico) – 2 0 0

Core Team Size – Onsite 9 7 7

Flex team Size – 33 33 30

Demand Planning Model 3 Month Forecast & 3 Month Invoicing

Case Study on - How Core Flexi Resource Model operates with an existing Customer


Key Tenants in Managing this engagement

Dedicated

Onsite

Delivery

Manager

Agile only

approach with

Dedicated

Agile Coach

Quarterly

Business

Review

Monthly

Resources

and Project

performance

Review

(LTF Driven)

LTF and

Hexaware will

jointly select

the core team


Daily Stand-up meeting End of Day review End of Week Review

Daily Meetings are good for initial planning, Later; these can be

incorporated into an “as-required” or merged into the Weekly

Meeting schedule. Service Line Leaders from the Hexaware

transition team, representatives from the Hexaware and Life

Time Fitness Transition Manager will participate.

The following agenda will be adopted:

Track Leaders meet with their respective

teams and adopt the following agenda:

Service Line Leaders from the Hexaware transition team,

representatives from Life Time Fitness and Hexaware will

participate.

The following agenda will be adopted

List deviations relating to interdependencies

Identify underlying issues to get buy-in from other track

teams (prioritization of issues will be moderated by the

Transition Manager)

Life Time Fitness Transition Manager will take

responsibility for coordination with Life Time Fitness

internal teams and third-party as appropriate for

addressing issues outside


Update the issue register

Review plan for the day

Review progress for the day

Identify deviations and underlying

issues

Record issues related to

interdependencies with other teams

Define plan for next day

Review status of deliverables and sign-off status

Review risks to the transition plan

Review unresolved issues by priority and age


Update the issue / risk registers

Review possibility of resource reallocation required to

meet plan

Review overall plan, and revise plan (if required, and as

approved by Transition Manager)

In addition to the above, we will have a fortnightly review conducted by the governance team to identify any directional changes to the transition plan. This meeting will

also be used to obtain any changes in the LTF organization priorities that may have an impact on the Transition Plan. Status Report will be prepared by the Transition

Manager for this review that will provide reports on progress in each track, open issues, and transition deliverables.

Transition Cadence & Participants


Transition Phase

Key Activities Acceptance Criteria / Sign Off

Pre Transition( Sprint 0 -2 weeks )

• Transition Kick Off Meeting (LTF & Hexaware)• Establish Access & Network Connectivity• Due Diligence of LTF Current Landscape• Assessment of existing Automation & Performance Scripts• Identifying LTF key SME’s for transition and prepare transition team and

plan• Team On boarding• Application Assessment• Finalize 3 past & existing CR’s in execution for the transition to know the

applications• Prepare High Transition Plan – This plan will continue to be refined

during the transition phases.• Criteria for Go, NO-Go decision across transition phases • Establish mode of transition

• Face to Face• Video Sessions –Skype, • Telephonic

• Refinement of existing Transition Tool Kit - Templates• Knowledge Acquisition document (KAD)• Communication Plan• Weekly status format

• High level transition plan• KT templates• Testing of connectivity and access to

applications• Sign-off on mode of KT

Transition Phases, Activities & Sign Off Criteria


Transition Phase

Key Activities Acceptance Criteria / Sign Off

Transition ( Sprint 1 3 weeks)

• QCOE SDET’s will be mapped across application streams and will obtain KT from respective LTF QA resources

• SDET’s will be a part of Sprint teams and will participate in all ceremonies such as backlog grooming, sprint planning, estimation etc.

• KAD will be updated and shared with LTF every Friday for review and comments.• Review comments for current week work will be incorporated during the following

week and before Friday.• Mitigate Risk and Issues• Sign-off of KAD for transition phase

• KAD document

Shadow Phase(Sprint 23 weeks)

• Hexaware SDETS will work in the sprints along with the LTF QA’s • SDET’s will actively participate in all execution ceremonies• Shadow the SME’s during project work• Update the KAD• Walk through of past CR’s / Projects• Analysis of historical data / tickets• Meeting with business / Stakeholders• Sign-off of KAD for Shadow Phase

• Sign-off on KAD



Transition Phase Key Activities Acceptance Criteria / Sign Off

Reverse Shadow

(Sprint 3 – 3 weeks)

• Hexaware SDET’s will be working in the sprints under the guidance of LTF QA’s• Will baseline metrics for QCOE• Update KAD• Hexaware team will work on CR’s and projects with support from LTF SME’s• Create test plan / test cases for the 3 past CR’s and current CR’s / projects• Submission of deliverables for past and current CR’s for review.• Sign-off of KAD for reverse shadow phase

• Sign-off on test plans / cases for past CR’s / Projects

• Sign-off on sample estimates for past / current CR’s

• Sign-off on KAD

Steady State (Sprint 4 – 3

weeks)

• LTF QCOE will be fully functional and will be operating in steady state• Hexaware team will me the primary contact for LTF with minimal support from

current SME’s• Agree on release date for current SME’s• Continuous update of KAD documents

• Sign-off on KT completion• Kick start steady state



Vendor to Vendor Transition Risks & Mitigation Plan

Key Risks Mitigation Steps

Loss of tribal and unstructured information that is not documented

LTF led orientation sessions with existing Vendor teams Request the vendor to document the information / knowledge in Wiki or Knowledge Documents.

Formats to be provided by Hexaware Set up the following structured approach for KT

Information gathering questionnaires and templates Use of extensive checklists to ensure that all information related to a particular area is captured.

Lack of co-operation from vendor contractors being displaced

Let the Re-badge team from LTF ( familiar) with this team lead the transition. Recommend travel for 3-4 core team members to LTF in MSP Overlap Offshore team hours with Europe work time to facilitate interaction Online Video Conference ( using GoToMeeting or Skype) to facilitate KT sessions Team building sessions online including gamification, Hexaware sponsored training of their choice etc.

Loss of critical resources during transition

Identify employee change readiness and engage them early mitigates this risk Prioritize knowledge transfer for applications which are business critical and which have dependency

on identified high risk individual SMEs from vendor team. De-prioritize knowledge transfer for non-business critical applications that have historically needed

low amount of testing hours Identify critical resources and prioritize knowledge transfer from them [SMEs] Loss of critical resources during transition to be highlighted and reviewed in transition and program

review meetings Back up resources from Hexaware team.


Sprints Sprint 0 ( 2 Weeks) Sprint 1 Sprint 2 Sprint 3

Dates (tentative) Jan 16 – Jan 31 Feb 1 – Feb 22 Feb 23 – Mar 15 Mar 16 – Apr 6

Onsite Offshore Onsite Offshore Onsite Offshore Onsite Offshore

Rebadged 2 2 2

Hexaware 4 14 13 14 13 14 13

Total 4 16 13 16 13 16 13

Grand Total 4 29 29 29

Transition Resource Distribution Plan

*Note: 4 Resources from Onsite Team will move to Nearshore (Mexico) after transition


• The Core team of 29 resources will be gradually reduced year on year attributing to efficiencies and productivity improvement that we will be

able to achieve from automation and other solution levers

• Hexaware recommends to operate a Flexi team on a T&M based on the 3 month rolling demand-forecast plan made available to Hexaware by

LTF

• This will enable LTF to be flexible and ramp up/down based on business demands without losing the core team and knowledge

Steady State Core Team Resource Distribution Plan

Years/Team Year 1

Year 2 Year 3 Year 4 Year 5First Six

MonthsLast Six Months

Location Onsite Nearshore Offshore Onsite Nearshore Offshore Onsite Nearshore Offshore Onsite Nearshore Offshore Onsite Nearshore Offshore Onsite Nearshore Offshore

Core Team 12 4 13 10 4 11 8 4 12 5 4 12 3 4 12 3 4 12

Grand Total 29 25 23 21 19 19

% split 41:14:45 40:16:44 35:17:50 24:20:56 16:20:64 16:20:64


Steady State Staffing model3

mo

nth

ro

llin

g f

ore

ca

st

Dem

an

d a

gg

reg

ati

on

Id

en

tifi

cati

on

of

Pro

ject/

Ap

plicati

on

wis

e T

est

Imp

era

tiv

es

Assessm

en

t o

f Q

A n

eed

s c

ate

go

rized

as

near

term

, sh

ort

term

an

d lo

ng

term

Category of

Resource

Ramp-up Ramp-down

Tier – I 50% in 4 weeks 30% in 3 weeks

Tier – II 75% in 3 weeks 50% in 2 weeks

Tier – II 100% in 2 weeks 100% in 2 weeks

Core

Team

Tier II - SDETs

Tier II – Security Testers

Tier II – Performance testers

Tier I

SDET, QA

Leads

Tier I

SDET, QA

Leads

Tier I

SDET, QA

Leads

2 - 4

Wee

ks

3-5

Wee

ks

2 - 4

Wee

ks

8 -

12

Wee

ks

Ram

p U

p T

ime

Reso

urc

e V

alu

e

Ra

mp

Do

wn

Tim

e

Knowledge

Management &

retention

Resource

optimization &

cross utilization of

Tier II resources

Catered to

varying resource

demand with

flexible ramp up &

ramp down

Total

health

Core

Team

ecommerce CRM

Tier III – Automation &

Performance Architects, Agile

Coach. Process Champion

1 - 2

Wee

ks

2-3

Wee

ks

Sample application tracks

Tier I (Application

SDETs, QA Leads)

Consulting,

framework design

& development,

implementation

Tier II (FLEX Team)

Tier III (On demand

shared support

Teams)

Capacity

requiremen

t


Transition Plan – Proposed Wave Approach

• Wave 1 - complex applications (BOSS, AEM, Total Health and Mobile Applications & LTF Suite (Exception)) – 3 Sprints

• Wave 2 applications will be CRM, E Commerce and Data warehousing – 2 Sprints

• Plan Validation : Hexaware will work with Life Time Fitness in the Pre Transition (Sprint 0) phase to validate the grouping of applications and will finalize the transition wave plan

0.5

LTF SUITE

BOSS, Scheduling & Registration

CRM, SharePoint

E Commerce

AEM

Total Health

Data Warehousing

Mobile Applications

1

2.8

1

2

1.8

0.5

0.1

3.5

Defects/story>2 = Complex

Defects/story >1 and <2 –

Simple & MediumDefect Ratio


BDD Process Activities

Business Goal Features

Step Definitions for Application

Code

Step Definitions for Automation

Code

Application Code

Automation Script and

Library

Build Results

Test Execution Reports

Living Documentation

Testable UsecasesCollaboration in the entire SDLC

Realtime Reports Early TestingAutomation as

much as possible

Automated Validation

Quicker FeedbackBetter Decision

Making