10X: Rate of New Cards Added

About this report

The Rate of New Cards Added report displays a line chart reflecting the number of cards added to the selected kanban since it's creation. The chart is generated by performing a straightforward counted plot of kanban cards by date, for the selected Kanban Board. Hovering over any point on the on the graph will display the count on the selected date.

This report is useful to both Product Owners and Scrum Masters for the purpose of examining the date that artifacts were added to the repository, as well for the management of WIP (Work In Process) and monitoring of Scope. 

Navigation

  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box. 
  3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.

Prerequisites

  1. A Kanban board must be defined.  
  2. The board must be loaded with features or stories.

How are report values calculated? 

  1. Count of ideas by date, constrained by the date of the first action against the Kanban and the last date any action was taken on any card on the board.

How to interpret this report

Tracking the addition of features and stories to a Kanban is important for the understanding of both scope and WIP (Work In Process). While scope is expected to change over time, the scope within an executing sprint/iteration should be relatively fixed. During planning the team shall have agreed on the work to be executed within the sprint/iteration time box, with the exception of new discoveries made as knowledge of the work to be delivered improves.

Expanding Work In Process (WIP) during an active sprint/iteration can be damaging to sprint/iteration performance metrics, as added work reduces velocity, increases workload and can be detrimental to team morale if excessive. Sometimes adding work to a sprint is unavoidable, when new discoveries are made during development. If this work is critical, it may need to remain within the current sprint, provided it can fit within the team's stretch goals and the Product Owner prioritizes the work above other active work. Otherwise, new cards should move to the next sprint as part of the planning cycle at the end of the current sprint/iteration. 

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.