Your Sprint Health Score combines Project Health and People Health for an overall measurement of sprint success. Below, we go into detail on 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.
.png?width=705&name=Sprint%20Health%20Deep%20Dive%20-%20Tickets%20(fewer).png)
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.