Uplevel’s Operational Metrics provide insight on the following:

• Release Count - the average number of releases to production per week over the selected time period or selected sprint
• Bug Allocation - the percentage of bug work over the previous sprint or time period.
• Sprint Completion Rate - the completion percentage prediction of your current sprint. (If you don’t use sprints, don’t worry. This will show the number of tickets closed during the selected time period)
• % of complex PRs - are devs making big releases or opting for smaller, more frequent changes?
• PR Cycle Time - the median time from development to release for a PR

FAQs

Where does this data come from?

The charts are powered by metadata from Jira and your version control tools. We’re looking at Jira issues for selected projects and PR data for selected repos. If you feel like data is missing, contact Uplevel Support.

What if my team doesn’t use sprints?

If you don’t use sprints, your charts will show data for the selected time period. Sprint Completion Rate will be replaced with Completion Rate and will show the amount of tickets that were finished in the selected time period instead of a percentage.

How do I know what’s “good”?

For metrics like sprint completion rate, the closer to 100%, the better. For Release Count, Bug Allocation, and % of Complex PRs, the answer isn’t always as clear. Along with setting goals for your team, it’s important to keep an eye out for any sharp deviations from the norm which could indicate something is off.

How can I track improvements?

You’ll see your previous sprint or week’s score for each one of these metrics. Stay tuned for trend line charts for each one of these metrics that give deeper insight into historical data.