Personal Velocity KPI

 

Personal-Velocity-KPI-on-Jira-Dashboard-Stack-by-Sprint-Rolling-State.png

 

 

Personal-Velocity-KPI-on-Jira-Dashboard-Stack-by-Priority.png

Step 1: Begin by defining a data source that identifies the issues to which a particular user has contributed.

Step 2: Choose ‘Story Points’ as the metric for evaluation.

Step 3: Select ‘Sprint’ for the ‘Display by’ field. To filter story points accomplished within the sprint, choose “Resolved in.”

Step 4: Whenever you opt to display results by Sprint, you’ll have to select a Sprint board to generate the report. This step is mandatory and ensures accurate sprint reporting.

Step 5: (Optional) Opt for ‘Priority’ for ‘Stacked by’ or any other fields that makes sense in your case.

Step 6: Activate the ‘Target’ section, and select the ‘% of Avg.’ tab.

Step 7: Choose Moving average as target level calculation type.

Step 8: Define the target level % and the number of sprints to calculate the Moving average (MA). In our example we are using MA derived from all past sprints. This minimizes short-term fluctuations, ensuring attention to long-term progress.

Step 9: (Optional) Activate the Warning Threshold Line if desired and determine the threshold – it can either be a fixed value or a percentage of the chosen target, depending on your preference.

 

Watch the video tutorial at our website: https://performance-objectives.com/kpi-personal-velocity/

Here are some examples of how to refine the selection of issues linked to a specific developer’s work (Step 1) using JQL in your Data Source settings. Please keep in mind that these examples are provided for illustration purposes, and you should adapt the filters based on your specific workflow.

  • status changed from “In Progress” to “Resolved” BY 5aaa3e5033719f2a50163739

  • status changed from “In Progress” to “Review” BY 5aaa43618fb3642a6fd215e5

  • resolution changed to “done” by 5aaa3e5033719f2a50163739

  • assignee = Account ID