Individual velocity chart for Scrum boards

Owned by Vasyl Krokha
Last updated: Nov 07, 2024 by Tetiana Kamenkova (Deactivated)
4 min read

Individual Velocity Chart displays velocity analytics of completed and active sprints broken down by individual team members.

Personal Velocity Chart answers the following questions:

  • What is the productivity trend of individual team members?

  • How does an individual deliver on their sprint commitment?

  • To what extent scope assigned to a team member is subject to change?

  • Is the work distributed among team members unequally?

Use it as one of gadgets on your Jira Dashboard.

Example of Personal Velocity Chart

Basic configuration

For detailed information about each chart setting, please, refer to Chart configuration | Personal Velocity Chart configuration

Let’s analyze the velocity of team members of the team called “Delta.” This team follows the Scrum process and uses story points (SPs) to estimate and track their progress.

Here is the configuration of the gadget. You need to specify the Scrum board, and you are ready to start:

Define your goal for analysis

Based on your analysis's goal, choose one of two "Group users" options while configuring the gadget:

 

Analyze sprint performance individually for each team member (option “Group users by sprint”)

This option is helpful if your goal is to answer the following questions:

  • How does each team member deliver on their sprint commitment?

  • To what extent scope assigned to a team member is subject to change for a particular sprint?

  • Is the work distributed among team members unequally?

  • How do team members compare to each other?

Analysis of Sprint 1

Initial commitment

At the sprint planning meeting, Andrew committed (Andrew is specified as an assignee in Jira issues) to 10 story points.

Final commitment

During the sprint, no work has been added or removed, and no work items have been re-estimated. Therefore, final commitment is equal to initial commitment.

Not completed work

Andrew did really well and completed all his work, so this metric’s value is 0.

Completed work

Andrew completed 10 story points, all the work assigned to him at the start of Sprint 1.

Analysis of Sprint 2

We see that the final commitment is 2 story points less than the initial commitment. This happened in this case because the bug (estimated at 2 SPs) assigned at sprint planning to Andrew was re-assigned to Alex when Sprint 2 was underway.

Andrew did a good job and completed all the work in the sprint.

Analysis of Sprint 3

Sprint 3 is the active sprint. Andrew has only 5 story points of work assigned to him at the planning meeting. So, when he finishes his work, he will be able to take some unassigned Jira issues into work, but this will change the “Final commitment” metric. Let’s see what the chart will look like:

So, from the chart above, you see that Andrew has taken 3 more story points of work.

Analyze team member’s performance across several sprints (option “Group sprints by user”)

On the chart below, you can compare the performance of Andrew and Alex in Sprint 2.

If you click on the area of the chart for a team member, you will see Jira issues that a particular team member has worked on. For example, let’s check the work for Andrew in Sprint 2: