What does it show?
This reports shows how many times the tickets are failing or passing. This chart can be generated per project, developer for a selected time interval.
For the selected issue status (Ready for QA in the given example) it shows what other statuses the issues transitions into.
Why is it useful?
Every SDLC has an ideal flow from the start status to the desired end status. However in some cases the issue has to go back into a previous status because of quality issues (failed code review, failed QA, etc.).
Testimonial:
"First, we were happy our code review acceptance rate is 96%. After that it turned out our code review process has serious flaws. Even bad codes passed passed too many times."
What does it show?
It shows an average of how much time it takes per status of a ticket. Project management tool Jira(EG)
Why is it useful?
Ideally you want your cycle time to be short.
It enables your team to reach fast, get a short feedback loop and iterate fast.
Longer cycle time means there are bottlenecks in the SDLC (Software Development Life Cycle).
Testimonial:
"Following the right metrix the team is now motivated to work on smaller tickets. That helped us to deliver faster smaller chunks of improvements and reduce the number of big risky deployments."
What does it show?
How the development teams’ overall contribution is distributed between the products,within a selected time period.
Why is it useful?
- Shows if the developers are working on the right products.
- Identifies how much efforts they put into each product.
- Helps to understand how development speed changes per project over time.
- Works without time-tracking.
Testimonial:
"We realized most of our engineering output was allocated to experimental projects and the real revenue-generating project was understaffed."
What does it show?
The total weekly code contribution within a time period, calculated as a score, per developer.
Score (code contribution): It’s the sum of the code contribution per developer. It can reach a maximum of 1 point/week/dev. 1k (or more) lines of code added or changed per developer per week equal to 1. That’s the maximum reachable score per week.
So 1 developer in 4 weeks can reach a maximum score of 4. Same score of 4 can be also reached as maximum by 4 devs in 1 week. Score is comparable between teams/companies as same logic is used.
Why is it useful?
Understand team members’ contribution over time.
Testimonial:
"Thanks to METRX we are able to measure how new developers are catching up. I helped us to optimize our onboarding and new hires started to be more productive sooner."
What does it show?
The team's’ code contribution per week within a given time range (Example: within the last year).
Why is it useful?
- Gain insight into the extent to which teams contribute through the deployment of new code and code modifications.
- This aids in identifying teams facing obstacles in their code contribution efforts.
Testimonial:
" Thanks to METRX we learned that one of our team had a declining trend in their productivity. Once we clearly saw it the team leader could jump in and started to remove obstacles. "
What does it show?
It indicates whether the coding contribution occurs during the creation of new features or the maintenance of existing ones. Provides information regarding the allocation of engineering resources between the development of new features and maintenance tasks.
Why is it useful?
In an ideal scenario, bug fixing should account for less than 30% of the total workload. Even without time tracking, we can assess the extent of engineering resources dedicated to maintenance, which offers a more precise measurement than merely tallying ticket numbers in JIRA.
Testimonial:
" The biggest take away was developers could work only on the roadmap up to 50% of their capacity. We had to better distribute work between developers so they can focus more on important developments. "
What does it show?
The estimated cost of the development of products based on the developers code contribution and salary in the last year. We can create the report on both commit/ticket/epic/project level.
Why is it useful?
We can offer a highly accurate estimate of the engineering expenses for product development even without the use of time logging.
Testimonial:
"We got valuable feedback immediately how engineering dollars are spent between projects and who are the most expensive developers. We analysed those and understand how to avoid expensive mistakes."
Where Can We Send Our Case-Study For You?
