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 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.
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.
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.
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.