Overview
The short answer to the question would be KPI (key performance indicator).’
Usually, a project will employ certain KPIs to facilitate the quantative analysis. By that, stakeholders can easilly tell how well the project is proceeding and how good the product is. However, there are some common challenges facing the project.
Top challenges
- Short-term project
- The analysis result may be distorted due to the insufficiency of sample data.
- Design the proper KPIs
- There are cases some KPIs are designed but eventually can not tell any meaningful story.
- It tends to be true that any single KPI can not reflect the truth.
- Collect data effectively and efficiently
- For an organization which does not have any process-wise tools in place, the cost of setting up a bunch of tools will be huge.
- In general, a project which will run for less than 3 months should not be applying any KPIs which require extra efforts to collect the data.
- Present the analysis result in a dashboard
- Without the support of certain tool, it is not easy to consolidate the analysis results into one and display to stakeholders.
- A dashboard should be able to tell the real-time status of the team/project, which requires everything should be done automatically.
- Displaying the reasonable charts in the dashboard is another requirement to be satisfied.
- Analyze the result
- Stakeholders who get low score tend to be resistent when asked to comment/retrospective
- Analysis should be conducted frequently but will cost a lot of efforts.
Sample KPIs
Below is a list of popular KPIs:
- Defect
- # of Defects Found/Day
- # of Defects Missed/Release
- # of Defects/Component
- # of Defects/Dev
- Top N defect hunter
- Top N defect creator
- % of Valid Defect – to measure the effectiveness of tester
- % of Fixed Defect – to measure the effectiveness of tester
- % of Priority Defect – to measure the effectiveness of testing
- # of defects/Build – to measure the trend of quality
- # of Days Defect remain active – to measure the productivity of dev&tester
- Test Results
- Passed rate
- Failed rate
- % of Test Cases Executed
- % of Test Cases Not Run
- % of Requirements Covered by Test Execution Round N