5 posts tagged with "nitroiq"

Introduction​

We've recently started adding new features to NitroIQ that help you identify performance issues in JIRA, and provide you with actionable insights to help you resolve them.

To that end, we are adding an entirely new section of best-practices and help to the NitroIQ online documentation. The aim is to help team leaders identify performance issues in their teams and processes and provide them with prescriptive guidance, using their own data, on how to resolve them.

Measuring Sprint Velocity and Burndown (or Burnup) is common practice in agile shops. It allows leaders to better resource and capacity plan, because knowing what your teams' past performance metrics, is a decent gauge of future performance in upcoming sprints.

Agile Churn: When changes in the list of tasks or scope occur during a Sprint (or iteration).

Churn in sprints is inevitable, but should not be a consistenly occuring event. Stories being added, removed, or story points being adjusted mid-sprint are a fact of life in a dynamic Agile environment, but minimizing disruptions to the team and deliverables should be the goal of every Agile lead.

More fun with JIRA data. ;-)

Can the number of status changes in a given Jira Issue be an indicator of missing or confusing requirements, bad resource management, or other team deficiencies that can affect sprint performance?

I've long run my teams using metrics calculated mostly using JIRA JQL and spreadsheet gymnastics. One of the most practical measurements of forward progress I've come to rely on is what we call "Innovation Rate", which is seeking to describe how much time is my product/engineering team spending on New Features compared to maintenance tasks or bugs.