Understanding JIRA Velocity Chart

  • Post author:
  • Post category:Blog
  • Post comments:0 Comments
  • Reading time:2 mins read

Problem

You might see multiple/difference burn down and velocity charts for the same Sprint.

Cause:

The most important thing to note about Jira Velocity Chart:

  • It’s board-specific, which means it’ll only include issues that match your board’s saved filter.
  • It’s based on your board’s column mapping. An issue is considered to be ‘To Do’ when it is in a status that has been mapped to the left-most column of your board. Similarly, an issue is considered to be ‘Done’ when it is in a status that has been mapped to the right-most column of your board.
  • Estimates from sub-tasks are not included in the Velocity Chart’s calculation. (Only estimates from parent tasks are included.)

Following are my example to understand JIRA Velocity Chart. I have 2 boards with different queries and column mapping.

The Development board:

This board will cover both Story and Task (issue types) and using a development workflow from Open (left-most column) to Dev Done (right-most column).

The Biz board:

This board only include Task and using Simplify Scrum Workflow from To-Do (left-most column) à In Progress à In Review à Done (right-most column)

Due to Task (issue type) might visible on both boards so that the burndown chart and velocity for the Sprint (WS5 Dev: Sprint 8) will be calculated differently based on the board-specific like pictures above.

Leave a Reply