1. A U G 1 3 , 2 0 1 3
C H E R A P A W A N N A S U K
C H E R A P A @ Y A H O O . C O M
Software Quality Team’s KPI

2. Type of KPI
1 2 3 4 5
Worst
Performance
Caution
Good
Achievement
Beyond
Expectation
True
Excellence
60% 70.0% 80% 90.0% 100.0%
KPI 1
KPI 2
1 2 3 4 5
Worst
Performance
Caution
Good
Achievement
Beyond
Expectation
True
Excellence
40% 30.0% 20% 10.0% 0.0%

3. 1. Include quality requirements into all deliverables
and ensure they get implemented
 Let’s see Acceptance Criteria (AC) in User Story
 Add Acceptance Criteria under Tester point of view
 Create Test Cases to check that all AC were
implemented

4. Measurement
No of AC get Implemented
No of AC proposed to Project Team
Sample (KPI 1):
-Product A, tester added 10 acceptance criteria at
the requirement phase.
- After tester verified the software product,
he/she found only 8 ACs were implemented
KPI = 8/10 = 0.8 (80%)  3 Good Achievement

5. Things to remember for 1.
 If the team agree not to develop the story in this
sprint, no need to count tester’s ACs in this sprint
 If the team can not implement ACs and inform tester
in advance with acceptable reasons, no need to count
that ACs too

6. 2. On time key project delivery with quality
 line chart test cases planned v.s. executed period
 Sample (KPI 1):
 Count Test Cases prepared in the execution period = 100
 Count Test Cases that actual executed in the period = 95
 KPI = 95/100 = 0.95 (95%)  4 Beyond Expectation
 Pick the best KPI if tester do test execution many cycles
Test Cases Executed
Test Cases planned

7. 3. Traceability and Coverage - True Money
 No. of Test cases/script map directly to requirements
and software product
 Sample (KPI 1):
 Total Test Cases = 300
 Total Test Cases map to S/W Product = 250 (create before
execution period)
 Additional Test Cases created during test execution S/W Product =
50
 KPI = 250/300 = 0.83 (83%) 3 Good Achievement
 Pick the best KPI if tester do test execution many cycles
Test Cases Map to S/W product (Before execute)
Total Test Cases

8. 4. Test Cases Effectiveness - True Money
 No. of defects not map to test cases/Total No. of
defects in each test cycle
 Sample (KPI 2):
 Count total defects found in the cycle = 20
 Count total critial defects found from additional Test Cases
created during test execution S/W Product = 3
 KPI = 3/20 = 0.15 (15%) 3 Good Achievement
No. of critical defects not map to planned test cases
Total No. of defects

9. 5. Defect Removal Efficiency - True Money
 No. of defects found in test phase/No. of defect found
in test phase + No. of defect in production in the first
10 days
 Sample (KPI 1):
 Count total defects found in all Test Cycles and found in
Production (the first 10 days) = 50
 Count total defects found in all Test Cycles = 45
 KPI = 45/50 = 0.90 (90%)  4 Beyond Expectation
 Count only defects that have no test cases cover and not duplicated
in the defects found in the development period
No. of defects in Test Phase
Total No. of defects (Dev + Pro 10
days)

10. Definition
 Critical Defect
 Impact to company’s reputation
 Impact to calculation that shown on any UI seen by the
customers
 Impact to system, make system crash or unable to continue the
normal operation process

11. Calculation Example

12. Test Manager’s KPI in each Project
 If there are many testers in the project, the
percentage that the team members will do correctly
at the first time will be KPI for supervisor.
 Calculate from multiply KPI of all tester in the project.
 Sample : Project A has 3 testers.
 Tester A, B, C got KPI no.1 for 90%, 95% and 80%.
 Test Manager will get KPI no. 1 = .90X.95X.80 = .68 (68%) 
Worst Performance