2 posts tagged with "backlog maintenance"

Why is backlog maintenance important?​

Maintaining a backlog, frankly just sucks.

It's a tedious task that teams rarely enjoy doing, but left unattended, will almost certainly lead to a variety of negative effects. I've often witnessed in my career that diagnosing a team's (product + engineering) inability to deliver on time, requires me to look at the backlog first!

The purpose of regularly maintaining (or grooming) a backlog is to ensure that the backlog is always up-to-date and that the team is always working on the most important issues. This is especially important for teams that are working on multiple projects at once, as it can be difficult to keep track of all the issues that need to be addressed.

Failure to maintain a backlog is a common occurence I've witnessed in my career and the effects can manifest in a variety of ways. However, the most common effects are:

• The team is working on issues that are not the most important (lack of prioritization)
• Product Management is unable to provide accurate estimates on when a feature will be delivered (lack of estimation) to customers and management.

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.