Annual Objective Objective

Ensure Better Customer Experience New development

Ensure Better Customer Experience Perform QA Testing to ensure customer expectations are
meet with actual development

Continous Improvement in QA stack Intorducing and Adoption of new tools

Continous Improvement in QA stack Draft SOP for QA assessments and bug fixation

Development, Execution and Maintaining of Test

Continous Improvement in QA stack automation scripts

Customer Experience Post Deployment QA

Customer Experience Closure of all QA as per agreed SOP & TA

Customer Experience Weekly, Monthly, CABS, IT announcements
 Measurement Criteria %

QA must be part of new requirment analysis and not only share

their input but also support to share test cases.
120 for, to be part of all requirements with detailed reports
110 for, to be part of 95% of requirments
100 for 90% of requirments 15%
85% for below 90% requirments
if reports are not shared then no contribution will be
considered.

All development should have maximum two cycle of QA.

100% bugs should be identified in round 1 and finally there
should not be any bug in UAT
120 for zero bug in UAT
110 for 10 bugs 20%
100 for 20 bugs
85 for more than 20 bugs
you will manage both QA and UAT reports with detailed
comparision

Adopton of at least 3 new tools at QA side

120 on implementation, utilization and improvement(training
and bug reduction)
110 on implementation, utilization 15%
100 for implementation only
85% for not achieving the timeline

50% for drafting new SOP/policy along with its review by 30-
Jul
25% for training and education dev on the new SOP by 10-Aug
25% for adoption and compliance of the SOP by 31-Aug
10%
120 on achieving all above
110 for missing one target
100 for missing two target
85% for missing all

Developing of scripts, utilizing and maintaining them in STLC

and SDLC process on allocated machine to add value in Testing
and Visibility
120 for all CR and developments
110 for 95% CRs 20%
100 for 90% CRs
85% for below 90%
reports must be shared otherwise it will be considered zero

120 for all deployments

110 for 95% CRs
100 for 90% CRs 20%
85% for below 90%

All bugs must be logged on Mantis BT (both production and

development)
120 ensuring closure of all Bugs according to QA SOPs
110 for closure of 95% timeline according to QA SOPs 7%
100 for closure of 90% timeline according to QA SOPs
85% for below 90% closure
100% for sharing reports in time otherwise 85% will be
awared 8%
100%
although this should be part of 2