top of page
Writer's pictureJiehwan Yang

[Internship] QA Data Analyst: SWE’s Bug Fix Performance

Updated: Feb 7, 2022

Introduction

In the summer of 2021, I worked as a data analyst intern in the QA team at a game-making company. As the name Quality Assurance suggests, QA team primarily deals with two tasks:

  1. Test runs

  2. Bugs

I was curious to know how efficiently Software Engineers were fixing bugs relative to each other. So I took the initiative to create a Powerb BI dashboard that tracks SWE’s bug fix performance.

 
Goal

The potential beneficiary of information about SWE’s bug fix performance is the SWE Team Lead & HR. The expected benefits are as follows:

  • Considering the characteristic of the bug, SWE Team Lead will be able to assign a bug to the most competent SWE, resulting in better bug fix rate

  • In performance appraisal, SWE Team Lead & HR can make a more objective evaluation of SWE’s competence in fixing bugs

We can compare the bug fix performance by all SWEs vs. SWE vs. SWE Team. Again, bug fix performance is measured by 4 KPIs:

  1. Average number of bugs fixed per SWE

  2. Average time taken per bug fix

  3. Critical impact of bugs

  4. Bug Fix Fail Rate

This page can be utilized:

  • If SWE Lead wants to compare how his SWE team performs compared to all SWEs or if he wants to compare how a specific SWE performs compared to the team or overall SWEs.

This page displays the overall Bug Fix Performance by each milestone. The Bug Fix Performance is evaluated by the following KPIs:

  1. Average number of bugs fixed per SWE

  2. Average time taken per bug fix

  3. Critical impact of bugs

  4. Bug Fix Fail Rate This page can be utilized:

    • MS 1 vs. MS 3

    • If the average number of bugs fixed per SWE increased from 16.65 to 31.91, we can infer that either more bugs occurred in MS 2 or the overall SWE capacity decreased in MS 2. Such inference will lay a stepping stone for further analysis into what really cause the increase in the average number of bugs fixed per SWE

 
Lesson Learned

It was a great opportunity to think from a client perspective and find answers to questions like

  • What's the current process that is inefficient and how can I contribute to solving that inefficiency?

  • What would I want to see if I am a SWE Lead?

  • How can I make a concise dashboard?


Comentários


bottom of page