Skip to main content

2 posts tagged with "issue churn"

View All Tags

· 5 min read
Roy Russo

What is Issue Churn?​

In the context of Agile software development, issue churn is a metric that can be used to measure the efficiency of a team.

Issue churn is a term used to describe the amount (issues or points) that have rolled over from one sprint to the next.

It is a measure of the amount of work that has not been completed in a given sprint. The higher the churn count, the less efficient the team is.

It's also important to represent Issue Churn as a Rate... that is, the amount of stories that are rolled over from one sprint to the next compared to the total number of stories that were planned for the sprint. This is a more accurate representation of the team's efficiency.

tip

Some Issue Churn is Ok

It's important to note that some issue churn is ok. In fact, it's expected. The goal is to minimize churn as much as possible, but it's not always possible to eliminate it completely.

· One min read
Roy Russo

New Docs How-To Section​

We recently added a new section to our online documentation called How-To. This section is designed to help you get the most out of NitroIQ by providing you with step-by-step instructions on how to use NitroIQ to diagnose and address common problems in Jira and developer performance.

The How-To section is broken down into distinct categories that mirror the functionality in the application. For example, if you are having issues with issue churn, you can navigate to the Diagnosing Issue Churn page to learn how to use NitroIQ to diagnose and address issue churn.

Future plans are to have these How-To articles linked directly from the application itself, so that you can quickly access them when you need them in the context of the application page you are on.