Scribd
Upload
117 views

GitHub Copilot

The document describes a trial of GitHub Copilot by an 11-member team over several sprints. Key metrics like throughput, quality, bugs and feedback were tracked before and after using Copilot. The trial aimed to evaluate Copilot's impact on productivity, code quality and identify areas of benefit.

Uploaded by

Natheem Safin
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
117 views

GitHub Copilot

The document describes a trial of GitHub Copilot by an 11-member team over several sprints. Key metrics like throughput, quality, bugs and feedback were tracked before and after using Copilot. The trial aimed to evaluate Copilot's impact on productivity, code quality and identify areas of benefit.

Uploaded by

Natheem Safin
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

GitHub Copilot

Report
GitHub Copilot | Overview

Start Date: December 4th


Team Involved: Yellow NPS Team (11 members)
Objective: To evaluate the impact of GitHub Copilot on the team's performance.
Key Performance Indicators (KPIs):
• Throughput: Comparison of the work completed during the trial sprint versus recent sprints without Copilot.
• Quality: Assessment of code quality and solutions developed with and without Copilot.
Methodology:
• Pre-Trial Preparation: Basic training will be provided to all team members to ensure effective use of GitHub Copilot.
• During the Trial: The team will use GitHub Copilot in their regular sprint activities.
• Post-Trial Evaluation: Performance will be assessed based on throughput and quality KPIs, comparing the outputs during the trial period with those from
recent sprints without Copilot.
Expected Outcomes:
• To determine the effectiveness of GitHub Copilot in enhancing team productivity and code quality.
• To identify areas where GitHub Copilot can be most beneficial.
• To gather team feedback on the usability and practicality of GitHub Copilot in day-to-day tasks.
GitHub Copilot | Team

NPS Yellow team members - selected for using GitHub Copilot

Sno Resource Email Id Technology

1 Dharmendran [email protected] SQL Server

2 Vignesh [email protected] SQL Server

3 Prakash [email protected] React Js

4 Rathikala [email protected] React Js

5 Udayakumar [email protected] React Js

6 Sarumathi [email protected] Full Stack Developer

7 Suresh Sankar [email protected] .NET

8 Siddharthan [email protected] .NET


GitHub Copilot | PR comments

We have calculated number of PR comments received in Sprint 4 and Sprint 5 which is before using GitHub Copilot and later team is using GitHub Copilot since Sprint
6. For few developers, PR comments has been reduced and few developers' comments are not reduced much due to new repo creation thus provide more number of
PR comments.

Resource Sprint 4 Sprint 5 Sprint 6 (GitHub Sprint 7 (GitHub Copilot)


Copilot)
Dharmendran 6 3 3 3

Vignesh NIL 5 NIL 8

Prakash NIL NIL 1 3

Rathikala 13 5 2 NIL

Udayakumar 17 NIL 4 NIL

Sarumathi 23 NIL 27 13

Suresh Sankar NIL NIL 3 7

Siddharthan 14 7 10 8
GitHub Copilot | Stories/Task commitment

Out of 8 developers, we have picked couple of developers to calculate the tasks they have been assigned, effort and the complexity.

Resource Sprint 4 Sprint 5 Sprint 6 (GitHub Copilot) Sprint 7 (GitHub Copilot)

Tasks Effort (Hrs) Story Points Tasks Effort (Hrs) Story Points Tasks Effort (Hrs) Story Points Tasks Effort (Hrs) Complexity
Estimated/ Estimated/ Estimated/ Estimated/
Actual Actual Actual Actual

Vignesh 4 44/48 SP – 5: (2); 4 30/40 SP – 5: (1); 7 50/56 SP – 2: (1); 6 39/36 SP – 5: (2);


SP – 13: (2); SP – 8: (3); SP – 5: (4); SP – 13: (4);
SP – 8: (2);

Rathikala 2 28/36.5 13 4 42/43.5 5 3 16/22.75 SP – 3: (1); 5 36.5/35 SP – 5: (1);


SP – 5: (2); SP – 8: (4);
GitHub Copilot | Bug Count

We have listed bug count between Sprint 4 and 7

Sno Resource Bugs Count


Sprint 4 Sprint 5 Sprint 6 Sprint 7 Bug Count
1 Dharmendran 2 2 8 7 12
10
2 Vignesh 4 0 1 3
8
3 Prakash 0 0 2 3 6
4
4 Rathikala 0 1 5 4
2
5 Udayakumar 5 1 10 11 0
an sh h la ar i ar an
dr ne as ka m ath nk th
6 Sarumathi 3 0 2 1 en ig rak th
i ku um S a
h ar
rm V P Ra ya ar sh d
ha da S re S id
D U S u
7 Suresh Sankar 3 0 1 1
Bugs Count Sprint 4 Bugs Count Sprint 5 Bugs Count Sprint 6 Bugs Count Sprint 7
8 Siddharthan 0 2 5 4
GitHub Copilot | Feedback comments on Usage

Resource Feedback
Dharmendran • Auto suggestions reducing the time of dev work.
• Explain the procedure well.
• Does not produce performance tuning for a SP, but it provides a performance tuning points which are basics.
• When requested for the flow diagram of the procedure which shows partial one.

Vignesh • Gives the best suggestion to complete the work.


• Reduced the minor mistakes in Codes while using Copilot.

Prakash • Simplified the code functionality.


• The fastest solution for complex type logic.
• Reduce the development time and improve the quality of the code

Rathikala • Auto suggestions reducing the time of dev work.


• Easy to find some optimal solution.

Udayakumar • Reduced the time for code development.


• We maintain the standard code across the app.
• Easily simplify the code with reduced no of lines.

Sarumathi • Improved coding standard.


• Auto suggestion is helpful for us.

Suresh Sankar • Improved coding standards and reducing the time of dev efforts.
Siddharthan • It is useful for adding summary comments in class, method, and model property.
• It is suggested to use proper standard variable names.
Thank you!

You might also like