The Sprint Health overview is a powerhouse of analysis from nearly every tool your team uses throughout a sprint. Daily refreshes give managers a clear view into how a sprint is trending — Is work getting done at the expense of team well-being? Did Monday’s redistribution of work lead to better Team Health by Friday? — and shows historical data for context.

Your Sprint Health Score combines Project Health and People Health for an overall measurement of sprint success. Below, we go into detail about both.

Project Health

Project Health considers sprint work reflected in Jira and Git, looking at factors like bugs, ticket carryover, tickets added mid-sprint, PRs lacking reviewers or merged without approval, and the prevalence of best practices like story points and descriptions. You can explore each element of Project Health below.

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.

All issue types are included in this score except Sub-tasks.

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.

All ticket types are included in this score except Sub-tasks.

Amount of tickets added

This considers the net number of tickets added to the sprint after it has begun. The addition of new tickets can be offset by the removal of other tickets. Unplanned work can affect the success of a sprint, so monitoring this can be helpful for teams to understand sprint risks.

All ticket types are included in this score except Sub-tasks.

Amount of tickets closed

This considers the velocity and proportion of tickets that were closed during the sprint. The higher the number of closed tickets, the higher the rating.

All ticket types are included in this score except Sub-tasks.

Tickets with descriptions

This looks at the number of Jira tickets that include a description. Adding descriptions to tickets is a best practice in Jira, so we recommend monitoring this metric for a healthy process.

All ticket types are included in this score except Sub-tasks.

Tickets with story points

This looks at the number of tickets that include an assigned number of story points. Story points are a best practice in Jira, so we recommend monitoring this metric for a healthy process.

All ticket types are included in this score except Bugs and Sub-tasks.

PRs merged without approval

The number of pull requests that are merged into a branch without approval from a reviewer during the sprint. Merging PRs without approval is a practice that should be avoided in most cases, so teams should aim to have a majority of their PRs merged with approval.

PRs without reviewers

The number of pull requests that don’t have reviewers during a sprint. It is a good practice to have reviewers for all PRs. This metric gives a score based on the ratio of PRs without reviewers and the total number of PRs.

Stuck PRs

The number of pull requests in a sprint that are considered stuck. Our calculations take into account PR complexity when deciding how long a PR must be waiting for review to be identified as "stuck." Less complex PRs will be defined as "stuck" after a couple days waiting for review, whereas more complex PRs require a week or longer in review. The fewer stuck PRs, the healthier the sprint.

People Health

People Health considers larger productivity or burnout metrics, like Always On, Context Switching, Deep Work, and Slack Interruptions.

Personal metrics include all people with tickets assigned to the sprint, not just your direct team. The following shows exactly how each item impacts the score.

Always On

Measures the number of people on the team who consistently work 30 minutes or more outside of their normal 8 hour workday during the sprint. Scoring well in this category means that your team is at a lower risk for burnout.