I am trying to get an authentic velocity calculation in Jira, which is also adaptable regarding which team members are working in the sprint and for how many days. (Taking absences into calculation)
For that I would probably need to assign (and further calculate) member specific capacities.
Or is there any other solution that comes to mind?
Portfolio for JIRA does support team velocity, team members hours per day, absences and holidays.
If you are using hours, the team velocity will be based on the team members weekly hours capacity.
If you are using story points, the velocity is set at the team level and team members contribution will be based on their weekly hours capacity.
so if I understand this right, there is no way of setting individual member capacities. (I know, this is not the right way of doing it, but absences didn't change anything on the current capacity predictions)
You can use the weekly hours to achieve this as the individual capacity will be proportional to the hours worked.
I have a doubt here, if someone works 20h/week with the sprint duration set to 4 weeks, what is the story points capacity over the whole month. Will it still remain 20, or will it be 80?
Also, say in a project I have three developers with everyone's capacity set to say 32h/week and total velocity as 96, a single developer is able to complete 66 points worth of task in one sprint when I optimize the roadmap, can you explain how this works exactly?
Hi @Kartik Parnami,
If someone works 20h/week, over a 4 weeks sprint the capacity will be 4 times that.
Now if you're using Story points, the capacity is set at the team level:
Let's say we give Team1 (with user1 and user2 as members) 60sp/week capacity and
- User1 works 20h/week
- User2 works 10h/week
If a sprint is 2 weeks, then you can do (60x2) => 120sp per sprint
User1 works twice as much as User2, so:
- User1 will have (120*2/3) => 80sp capacity per sprint
- User2 will have (120*1/3) => 40sp capacity per sprint
In your second example:
96sp / week velocity, assuming a 4 weeks sprint this means a capacity of (96*4) => 384sp / sprint
With 3 developers working the same amount of time, it means they have an individual capacity of (384/3) => 128sp/sprint (so more than enough to cover 66sp per sprint).
Hope that helps clarify things!
- Is the velocity I enter for a team, in the "Teams" section, per week or per sprint (in my case 4 weeks)?
- Additionally, I don't see an optimal allotment of developer time, the developer has free bandwidth according to the weekly hours put in, yet no task is planned for a sprint whereas some tasks are planned for a later sprint.
- No tasks are assigned to the active sprint even when the developer has some bandwidth.
- I tried manually assigning say "Feb sprint 2019" to a user which stretched from 01/Feb/2019 to 28/Feb/2019, yet on clicking optimize it shifts it to a later target start date, target end date and sprint. How can I fix this schedule, I probably want it to flag this issue to me, but not change it.
You can try using our new plugin located directly in the backlog , and enables you to configure daily capacity and absence for each team member for the sprint, and view the capacity as it fills up to its limits.
Sorry for the late response! Your software looks really promising, but again here you can only use available hours as opposed to calculating actual velocity.
Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-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