JIRA is giving me a good view in our team velocity (for example: 30 points a week), but I also want to check the individual velocity (so what's someones peronal velocity) due to different components and varying availability. How can I track this?
I would like to raise the question why? Why is the measurement of Individual velocity needed in the first place?
In agile, the focus is to deliver as a team rather than as individuals, which is the reason, stories are planned as a usable incremental feature rather than a task.. like you dont plan a story to complete a java class. The story focuses on the feature, the user / application gets. A few more thoughts on why this is an anti-agile practice.
Individual velocity may de-motivate people, and many managers having it in hands will use it incorrectly. It is very common to revert back to muscle memory of waterfall days and make assignments instead of commitments.
In the end, I think individual velocity is anti-Agile and harm to the team commitment, collaboration and breaks the rule collective ownership. Rather than individual velocity, I would recommend leadership to measure the contribution of individual to the team’s productivity, automation, competence, speed to understand the contribution.
I might have opened a can of worms here.. Please Feel free to disagree so that a healthy discussion can be done on this topic.
All the more reason not to use Individual Velocity.
1. Velocity is a relative measure whose prime purpose is to abstract away from absolute estimates
1. Velocity is a team metric measured at story level and not intended for measuring Individual performance
1. Scrum is for small teams(~ 8 members). If a team is not able to identify an underperformer in a Scrum team, its the HR practices that needs to be relooked rather than using underhand techniques like Individual Velocity.
1. There are other proven and better ways of identifying an underperformer!
1. Lastly, I have seen underperformers pulling up socks and improving vastly just because of Daily standups (where the same status cannot be repeated every day) & Retrospectives (where issues get pointed out and remedial measures are planned)
Last: Watch this video on why this is detrimental to project health!
There's a lot of this thinking around scrum and it frustrates me.
Jodi is asking for a view of data, nothing more. It's useful to have data when analysing performance. You don't rely on one data set, you take in hard data such as individual velocity and soft data such as you'll find in retros and standup or by talking to the team and in 1:1s.
The notion that velocity is a reletive estimate and therefore not an appropriate data point doesn't add up, since the point of doing velocity estimates (scrum poker etc) is that, firstly you get better at it, and second the variance cancels out over time, sometimes you're low and sometimes you're high. Therefore, if in a team who are estimating together, you find an individual who is constantly achieving less story points you can look for a reason. Perhaps that person is way more involved with PRs - there you have a reason, move on, or perhaps that person isn't performing - you talk to them in 1:1s and resolve.
The point is the data, all data collected in total across multiple touch-points, helps you manage and it's always useful to have data at your fingertips from as many sources as you can get if you want a performant team.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events