Understand insights on the backlog in next-gen projects

The following information only applies to next-gen, scrum projects and Premium plan customers. This is a beta feature.

To check your project type, look at the bottom of your project’s left-hand sidebar. If you don’t see an icon stating You’re in a next-gen project, then you’re in a classic project. Check out our classic project documentation.

Insights on the backlog provide support for you and your team during sprint planning sessions and retrospectives.

Sprint commitment

A cropped screenshot of the sprint commitment insight card. Avg points from past 5 sprints are compared to the sprint target.

Review your previous sprint commitments during your sprint planning sessions to get an idea of past trends. Look for your ideal range, and aim to assign the target amount of story points or issues.

The sprint commitment insight card looks at the average story points, or issues, completed in the last five sprints to recommend a target range for future sprints. The card respects the estimation statistic that’s enabled for your project.

Learn how to enable estimation in a next-gen project.

As you plan, the story points or issues you commit to the sprint will be tallied and compared to your target. Recommendations are automatically calculated if your commitment falls outside the target range, making it easy for you to adjust your scope as you plan.

To see what was committed to in previous sprints, hover your cursor over the grey bars.

Issue type breakdown

A cropped screenshot of the issue type breakdown insight card. The card shows the top focus for the sprint is "task".

Use the issue type breakdown for sprint planning sessions. Assess the balance of work from previous sprints to adjust, or maintain, your focus next time around.

See the issue type breakdown for your sprint. As work is assigned, the visualization and callout adjust, so you can understand the balance of different work types. The card only displays issue types allocated to the sprint.

The callout lets you know which issue type appears the most in the sprint. This is useful during retrospectives, so you can reflect on recurring, time-consuming issue types.

During planning sessions, assess your top issue type to make sure your team isn’t heavily focused on bugs and tech debts. Too many bugs and a hefty tech debt could be a cue for your team to focus on quality or block out time to resolve debts.

Hover over the bar associated with each issue type to see the exact number of issues allocated to the sprint, and the percentage it contributes overall.

Last modified on Jan 18, 2021
Cached at 3:51 AM on Mar 9, 2021 |

Additional Help

Ask the Community