Pull-Requests KPIs

[Amzani]

Problem

At AsyncAPI, we prioritize the prompt acknowledgment of new contributors who submit pull requests, offering timely code reviews, and ensuring efficient code merging. We view this quick turnaround time for reviews as a vital indicator on how successful we are at engaging our community of contributors.

Solution

To solve the problem we first need to get visibility around our key engineering metrics that are split into 3 main categories:

1. Pull-Requests KPIs
2. Release KPIs
3. Issues Interaction KPIs

In this Bet we will focus on Pull-requests KPIs

Pull request flow

Metrics we want to track

We would like to track theses metrics in the repos we monitor

Feature lead time

merge (date) - first commit (date)

PR lead time

merged (date) – opened at (date)

Time to first review

first review created at (date)  - last commit created at (date)

Review time

last review created at (date)  – first review created at (date)

Last review to merge time

merged (date) – last review created at (date) 

Solution design

1. Store the metrics in a database // or analytic service (preference for solutions that supports open source)
2. Users must see the metrics in a dashboard to track them over time
3. The system must offer alerting capability (slack integration)

Rabbit holes

Not known for now

Scope

• Define the technical solution for PR KPIs #805
• Setup pullpo.io #829
• Deploy

Out of bounds

The alert system should not be hard coded, it must offer the team the possibility to define the KPIs as part of the working agreement (PRs should have first time review < 24h)

Success criteria

We are able to get visibility on the metrics and reduce the review time.

[shapeit-bot]

Thanks for creating a new pitch 🥳. You can now create or link existing scopes.
You can create new scopes in two different ways:

Option 1

1. Edit the Pitch or Bet issue
2. Add your scope under the scope section

See this example

Option 2

1. Create a new issue
2. Add this keywork in the description related to #ISSUE_BET_NUMBER

See this example