I want to calculate the number of story points closed between 2 dates and used the number of team members to calculate velocity.
Something like (Sum the number of story points of issues closed between day-X and day Y and divide it by Z (number of people in the team).
Any help on how to achieve this will be welcome.
Hello Zigi, Alessandro from ALM Works here.
You can actually easily calculate what you've been mentioning by building a new structure and getting into the board, issues from a defined period by using JQL.
From there, you can group the issues by assignee and use some formula columns to the math.
Note that this is a mere example I quickly built, Much likely, there are different approaches you can take with Structure to achieve the same result. That said, here's what you can do:
Project = STR AND (status changed to Done during ("2020/11/09", "2020/11/12") )
I limited my query to a project in this example, but you can do it with multiple projects if you'd like to.
You can modify the timeframe in the "During" parenthesis as you need.
At this point you should already have a structure showing the issues resolved on the specified period and how many Story Points have been accumulated per assignee.
The next step is to figure out, using structure, how many Assignees the structure you've built have:
child of root(This query will be used to dinamically count how many assignees appeared in your structure using the Structured JQL feature)
Finally, create a new "Formula ..." field to calculate the average between assignee by story points:
IF(Type = Project; Story_Points + Resources; "")(If any of the fields appear in red at the Variables list, click on them and select the corresponding column)
Finally, you should be able to see the calculation you've mentioned in this new column.
(Note that, if you would like to, you can remove the columns created previously, as Structure stores the calculations used on the 'Velocity' column)
I hope this helps!
Hi @Zigi Fibert
What problem are you trying to solve?
What you are describing is not the velocity of the team; the velocity would be the amount of work the team finished during a sprint, not one person on the team. There are existing reports built into Jira to measure velocity over time.
Thanks for explaining, @Zigi Fibert
Unless you have a lot of churn in the people who are on the team or in the lengths of the sprints, why not just use sprint velocity, convert to "months" and adjust it for capacity? (Ignoring old data and months with many holidays.)
For example, if your team's sprints are 2 weeks long, and:
Your average velocity is (15 + 21 + 18) / 3 = 18
Your average monthly velocity (2 sprints) is 36
For capacity planning impacts, ask people to identify their out of office/vacation/holiday time far enough in advance for whatever planning timeframe the team needs, at least before each sprint's planning.
We not doing sprints but a continuous development over a period of a few months. This is why I want to measure story points closed within a time period.
We also have up to a 20% increase in resources towards the end of the delivery estimate.
I can handle that once I know how to calculate the SP closed within a certain period of time.
Thanks, @Zigi Fibert That helps clarify quite a bit!
Okay, your team is using continuous flow practices (Kanban) rather than iterations with sprints (Scrum). Often teams using Kanban measure in terms of Cycle Time and Throughput (the equivalent of Velocity for Scrum) to help improve and to forecast. So, how do you get that information?
The built-in reports can help, but are not (in my opinion) accurate representations of Cycle Time or Throughput for teams. Two alternatives are marketplace add-ons for dashboards or export/analyze in a spreadsheet. With add-ons it may be unclear what is being measured; with a spreadsheet you know exactly what is happening (because you built it).
Regarding the increase in team capacity by 20%, you do not need a by-person count to forecast for that. Instead just multiple your monthly throughput by 120%. Of note, adding more people to a project rarely increases immediately due to on-boarding. More often, throughput goes down before it goes up, so consider that for your planning.
Hello Community! My name is Brittany Joiner and I am a Trello enthusiast and Atlassian Community Leader. In this video, I'll share my favorite Trello templates. Templates mentioned in ...
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