How can we do sprint capacity planning?Do we have any reports for Capacity vs Velocity for tracking?

[Saranya A]

Trying to get capacity planning done for my team using Jira cloud. Also, for Sprint Metrics tracking looking for reports to publish Capacity Vs Velocity for every sprint. Do we have any existing capabilities supporting this need without any plugins or additional software? Kindly assist. 

[Bill Sheboy]

Hi @Saranya A -- Welcome to the Atlassian Community!

By "capacity planning" do you mean:

• when the team is all present for work for the entire planned sprint, our capacity is fully available (e.g. 100%)
• when one or more people are out of office (e.g. vacation, holidays, training, etc.) our capacity is reduced
• using our "capacity", velocity history, and what we know of the requested work, we make adjustments during sprint planning to the goal and work we can deliver

If that is what you meant, I know of nothing built-into Jira Cloud to support that.  Instead teams have a conversation during sprint planning to adjust.  There are probably marketplace addons to make recording that information easier.

Kind regards,
Bill

[Saranya A]

Thank you, Bill.

I am sorry I should have mentioned it as Capacity tracking than planning. Yes the capacity varies each sprint based on team members allocation / availability. 

We are trying to get a report on Total capacity vs Total Story points delivered for every sprint. So that we can can calculate average velocity of the team and per resource as well.

Also, over sprint planning we are looking for a factor to define how much story points we can accommodate? In Rally we can see the total capacity available and plan stories accordingly. 

Looking little further Advanced Road maps seems to solve this on a high level.

https://support.atlassian.com/jira-software-cloud/docs/monitor-capacity-on-your-advanced-roadmaps-timeline/

I am trying to set this up for our team and see if this is solving the purpose.  

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

What are you looking for with this "capacity planning"?    In general, the velocity can be used as a measure of capacity, as it tells you how much the team has been getting through in each sprint, and hence how much you could expect them to get through.  In fact, that is what velocity is for - guiding the team's selection of items for the next sprint and keeping the volume within what they can achieve.

So before I can start talking about reporting in any detail, I think we need to know a bit about how you want to do your capacity planning - what data are you looking at to inform the planning (and have you already got the data in Jira)?

[Saranya A]

Hi Nic,

Thank you for checking.  As Jira is not supporting a sprint level adjustment of velocity based on available capacity, this is a  time consuming manual process so far for us.

We are trying to get a report on Total capacity vs Total Story points delivered for every sprint. So that we can can calculate average velocity of the team and per resource as well.

Also, over sprint planning we are looking for a factor to define how much story points we can accommodate? In Rally we can see the total capacity available and plan stories accordingly. 

We are looking if setting up Advanced Roadmaps can help us. 

Any guidance on this or other ways will be of great help.

[Nic Brough -Adaptavist-]

> As Jira is not supporting a sprint level adjustment of velocity based on available capacity

It's not supposed to, you're not supposed to be adjusting velocity, it's a number that comes out of your historical data.

Story points are not supposed to be used for capacity either.  Your velocity based on Story points is there to help plan how much the team can get done in the next sprint.  The simple answer to "how many story points we can accommodate" is "take a look at your previous velocity and follow the number it gives you.  (A really easy trick for those of us who are worried about planning for holidays is to log holiday as an appropriately sized story for the sprint and put it into the sprint before worrying about the rest).  

Capacity planning is mostly an irrelevance to Scrum, and shouldn't be done on Story points anyway.