nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using Advanced Roadmaps for Individual capacity planning

Juan Du Toit

We have a client that uses AR.

They have teams that constantly change and need to see the individual capacity for current and future projects.

The only way I can think of doing this is by creating individual teams per member. This would mean creating 80 teams if this gets rolled out to the rest of the organisation. I don't think it's a good idea as it seems very complicated.

Questions:

Can this be done using AR if teams are not really working in teams?
What is the best way to do this without hacking AR and overcomplicating it?
What alternatives are there?

Any inputs will be appreciated.

Regards,

Juan

Accepted answers

Dave

Hi @Juan Du Toit ,

Thanks for raising this question.... I'm on the Advanced Roadmaps team and I can let you know that this is something that we're looking into in detail at the moment. So although I'm unfortunately not able to give you any great solutions at the moment, any insights you can provide into the various use cases and you and your client's experience would be incredibly valuable.

The workaround that you're suggesting (one person teams) is actually something that we know people do and arguably works but is obviously not an idea solution. We believe that there is a strong appetite for some kind of individual capacity management but there are concerns about providing tooling that might be used against an individual (i.e. saying that person A does more than person B - even though there might be perfectly valid reasons for doing so such as the experience, working hours or contribution across multiple teams).

In order to address team based fluctuations in capacity we have provided a way in which you can adjust the velocity of future sprints (i.e. to account for absences or people joining or leaving a team) but ultimately that relies on the user to actually calculate the velocity to enter.

It would be interesting to understand what types of individual capacity settings are required here, i.e. is this for time or points based capacity, are you looking to account for planned absences (like vacation), increase in capacity over time (to account for individual development), planned secondments into or out of the team, split team contributions (reducing the contribution to each team) or specifically setting the velocity of an individual.

Regards,

Dave

All comments

Dave

Hi @Juan Du Toit ,

Regards,

Dave

Juan Du Toit

Hi Dave,

Thanks for getting back to me in such a timely manner!

Let me work with my client to provide you with more information. Will you be interested in having a call directly with them?

Kind Regards,

Juan

Dave

Hi @Juan Du Toit ,

Sorry it's taken a few days to get back to you on this. I've reached out our Product Management team about your offer, they might respond in time but setting up a call like this is not something that I'd typically be involved in. However, we do appreciate the offer!

Regards,

Dave

Marius Grigorescu

Hi,

This is a features we are also interested in. We have a reasonable big team and we're trialling Advance Roadmap Planner. Not having the possibility to set individual capacities is one big limitation for us.
Having teams of one person each can be a temporary workaround, but as you said it not a robust solution.

Thanks,

Marius

Tara L Conklin

@Dave

First, I just added my comments and vote to JIRA-20434. We just upgraded to Jira Premium because of Advanced Roadmaps and without the ability to adjust a plan to account for individual PTO, holidays, training etc it seems impossible to create any semblance of an accurate plan. The team capacity is 'set it and forget it' and applies to the entire plan, which is simply not logical.

How are the teams at Atlassian creating accurate plans in AR? How are you accounting for a team member out due to vacation or unexpected medical issues, or shorted staff due to the holiday season or mandatory training? These are temporary adjustments that need to be accounted for and right now that is simply not possible in Advanced Roadmaps.

Second, Estimation on AR is only calculated based on days - Estimate (d) - yet unless we don't understand the intended use case of this field it also doesn't allow us to create accurate plan dates based on estimates. We have some teams that plan capacity on hours, some use the Fibonacci sequence for scrum, and another uses a modified scrum sequence. All of these are valid Scrum capacity planning methods and are not supported in the Advanced Roadmaps.

As another user stated in a different thread, our teams only plan their capacity based on a 6-hour work day. I'm a certified scrum master and coach and best practices always encourage teams to allocate part of their workday to

• email

• meetings

• unexpected interruptions

• breaks etc

if you plan to an 8-hour workday this inflates the available capacity of the team.

Advanced Roadmaps also doesn't account for a less than 8-hour per individual capacity.

This is all essential to accurate and useful planning and I do sincerely encourage your team to incorporate these into AR at your earliest convenience.

(PS: I'd be happy to come to Atlassian to help work on it with you) :0) 😉

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

advanced-roadmaps