Astronuts provides up to 60 customizable dashboard for engineering metrics, here are the default core metrics you will find in your dashboard.
This answers the question, “How effective are my teams in delivering value v/s efforts spent?”. It is the ratio of the functional value of software produced to the labor and expense producing it. In Jira terms it would be total story points delivered in a month/week per person day.
Its the number of product/software features being worked upon at any given point of time
Its the number of product/software features delivered in the last month. Its a pure number and its beneficial to chart it over time as a second level detail.
Its a ratio of the effort spent in delivering customer facing features v/s effort spent in fixing bugs or addressing technical debt. High business impact is desirable, and a gradual increase over time is desirable.
Its the duration between a feature being requested and the feature being deployed to production. It can be measured in days. Since a team might be delivering many different features, its an average of the lead time of all features deployed to production last month.
Its the duration between starting development on a feature and the feature being deployed to production. It can be measured in days. Since a team might be delivering many different features, its an average of the cycle time of all features deployed to production last month. This is a pure number like 4 days or 0.25 days.
t indicates the currently active Pull Requests (opened during a given time period) into which developers are committing code changes.
Its a pure number and is the number of deployments done to a production environment per month or week.
Its the number of defects or bugs reported every week or month. We will consider a monthly number.
ts a pure number. Its indicative of how well software is designed and how maintainable the codebase is. Its helpful to chart it as a trend month over month. It should be a very low number.
This is a custom “macro” level metric which looks at all other metrics, applies a certain algorithm and comes up with a number between 1 and 100.
Its a grading system from A - F. Grade A being the highest. Its an indicator of overall quality of the code. I
Its indicative of how well software is designed and how diligent developers are to maintain high coding standards. Its helpful to chart it as a trend month over month. Ideally it should be zero.
Its an indication of how well tested the software is. The testing is done by automated tests that developers need to write along with actual code. Its helpful to chart it as a trend month over month. It should increase over time and should ideally above 80%.
Rorem ipsum dolor sit amet consectetur. Proin dignissim tortor mauris viverra sed volutpat mauris. Amet nisi amet commodo adipiscing ut imperdiet nunc.
Total number of security vulnerabilities identified.
Total number of security hotspots found in code which has long term impact
An overall health score grade from A - F. A being the highest
improve your engineering metrics and get actionable insights