Overview and other comprehensive references
This article does aim to be a quick reference and give an overview to navigate the Athenian product. The article however does not aim to be a comprehensive list of all Athenian features and metrics, which are much more extensive, and new ones are frequently added to the product.
For the full product experience with all features, we recommend you schedule a demo meeting.
For in-depth explanations of key metrics, why they matter and how can you improve them in your organization, see our full Metrics Explained series.
For articles on how to better understand and improve your organization's practices, refer to our Continuous Improvement Methodology series.
Top-level engineering metrics
Elapsed time between the creation of the 1st commit in a pull request and the code being used in production.
Sum of the average time required in each development stage.
Number of pull requests released, counting in the Lead Time.
Number of people involved in delivering software.
Software Development pipeline stages
Work In Progress
From the 1st commit of the pull request until the review is requested.
From the moment the review is requested until the pull request is approved.
From the moment the pull request is approved until it is merged.
From the moment the pull request gets merged until it is released.
Work in Progress stage
Comprehensive overview of the stage key metrics: from the 1st commit of the pull request until the review is requested.
Pull Requests Created
Shed light on when, where, and who is opening pull requests.
Pull request throughput through time.
Identify the repositories that show the biggest number of pull requests created.
Pull request throughput of the team.
Pull Request Size
Target the best engineering practices by reducing and monitoring pull request size.
Distribution of pull requests by size in terms of lines of code.
Biggest Pull Requests
Shed light on the biggest pull requests which slow down the delivery pipeline.
Pull Request Ratio Flow
Track the ratio of opened/closed pull requests per day and anticipate congestions in the delivery pipeline.
Code Bypassing Pull Requests
Evaluate the amount of code that bypasses pull requests i.e. the review process and CI.
Comprehensive overview of the stage key metrics, from the moment the review is requested until the pull request is approved.
Wait Time for 1st Review
Lower the time pull requests stay idle, waiting for the 1st review.
Understand the role of each team member in the review process.
Comprehensive overview of the stage key metrics, from the moment the pull request is approved until it is merged.
Identify in which repositories pull requests take longest from review approval to being merged.
Comprehensive overview of the stage key metrics, from the moment the pull request gets merged until it is released.