Below are the various project metrics captured by data Uplevel is capturing via Jira and how those metrics may impact the overall health of your team's sprint.

Amount of bugs in sprint

This looks at the amount of bugs in the current sprint compared to the total number of issues. Each team has a baseline for what is considered “normal”, based on historical ratios. Anything above that normal level will move the dial towards concerning, while anything below will trend towards excellent.

Amount of tickets carried over

This reflects the amount of tickets in the current sprint that were carried over from a previous sprint. Tickets being carried over might signal that the assigned work in the previous sprint was more than the team could take on. Having fewer tickets carried over signals that the sprints are being planned well, taking team velocity into account.

Amount of tickets added

The amount of tickets added to the sprint after the sprint has started. Unplanned work can affect the success of a sprint, so monitoring this can be helpful for teams to understand sprint risks.

Amount of tickets closed

The proportion of tickets that were closed during the sprint. This measures velocity, so the more tickets that are closed during the sprint, the higher the rating.

Tickets with descriptions and story points

The number of tickets that include a description and an assigned number of story points. Adding descriptions and story points to tickets are Jira practices that should be encouraged, so this metric is intended to monitor that activity.