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

People Health Factors

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

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. For more details, visit our user guide.

https://resources.uplevelteam.com/hs-fs/hubfs/Sprint Health Deep Dive - Always On.png?width=705&name=Sprint Health Deep Dive - Always On.png

Context Switching

This measures the number of people on the team who had an increase in context switching compared to their unique baseline. Context switching is a metric that is closely linked to burnout, so it is important that team members aren’t being spread too thin over too many different projects. For more details, visit our user guide.

https://resources.uplevelteam.com/hs-fs/hubfs/Sprint Health Deep Dive - Context Switching.png?width=705&name=Sprint Health Deep Dive - Context Switching.png

Deep Work

This metric looks at the daily available Deep Work time (i.e., two or more hours of uninterrupted time for devs to focus) during the current sprint, compared to recent past sprints. When a team has the same or more Deep Work time than past sprints, this score is higher. When Deep Work time is dropping, this score is lower. Having insufficient Deep Work can impact sprint velocity and make it difficult for devs to get work done. Monitoring the amount of time devs have to focus will play a big part in sprint success. For more details, visit our user guide.

https://resources.uplevelteam.com/hs-fs/hubfs/Sprint Health Deep Dive - Deep Work.png?width=705&name=Sprint Health Deep Dive - Deep Work.png

Interruptions

This measures the amount of Slack or Teams interruptions that the team received in Deep Work time during this sprint, compared to past sprints. Distractions can cause a sprint to be at risk, so monitoring focus time can help get more done. For more details, visit our user guide.

https://uplevelteam.zendesk.com/hc/article_attachments/4416474970509/Untitled.png

Use Sprint Health, Project Health, and People Health to re-prioritize sprint tasks when plans change and load-balance work to support a healthy team.