Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,368
Community Members
 
Community Events
176
Community Groups

Capacity Planning shows "all green" until last iteration

I am playing around with Kanban capacity planning visualization in Advanced Roadmaps and it looks like that instead of spreading the estimated hours evenly across the iterations  (ie. weeks) between start and end date, Advance Roadmaps always assumes 100% of the capacity per iteration up until the last, when it all piles up and turns red.

Is there any way to have this show similar to eg. BigPicture? There I could immediately see, if a task is overloading a team and how allocating more time could make it feasible. Am I missing something (or even the point) here? Thanks in advance!

2022-07-04 16_11_14-PPM IT Prio & Planning - Advanced Roadmaps.png

3 answers

1 accepted

1 vote
Answer accepted

Hi @Fabian Dengel

The behaviour you've described is the way that we currently expect Advanced Roadmaps to work, and unfortunately there's currently no way to configure this to spread the capacity evenly among the sprints.

That being said, this behaviour was actually raised internally by one of my colleagues recently as behaviour that's unusual, so I can confirm that this is on our radar and we certainly agree it could be better! At this stage I can't make any assurances that this will be worked on in the short term, but having feedback like this does help us prioritise our work.

Sorry I can't provide any better solution at the moment! Do feel free to reach out with any further feedback or questions you have about Advanced Roadmaps though.

Cheers,

Daniel

Hi @Daniel Capizzi 

Many thanks for your feedback! Appreciated to hear it straight from the team, as this will help to manage customer's expectations towards the available options.

I have opened a Feature Request in the meantime via https://jira.atlassian.com/browse/JSWCLOUD-23210 to see if there is more interest for this potential change in the community, but will mark this as answered for now.

Thanks again and kind regards
Fabian

Like # people like this

Prior to Advanced Roadmaps being rolled into JIRA, (when Roadmaps was a separate product) the feature worked exactly as desired... We used it for capacity planning and forecasting. When we created a new project and added estimated initiatives for each team it would show places in the timeline where the effort would exceed certain teams capacities.
Now that we are looking at moving to 9.2, we see this 'new functionality' as a regression that will break our planning processes. This prevents us from moving to 9.2 and will keep us on an older version until this is resolved (even though I know Atlassian does not see it as a regression)

 

JIRA 8.13 Roadmaps

813_capacity_planning.png

JIRA 9.2.0 Roadmaps

920_capacity_planning.png

A quick follow-up... not sure if this fixes for everyone, but I found a checkbox that turns off this "feature"

I am using 9.2 Data Center

Administration -> Manage Apps -> Advanced Roadmaps Early Access Features

Uncheck "Enhanced capacity distribution"

roadmaps_capacity_beta_checkbox.png

JCameron I'm New Here Jan 16, 2023

You're going to even more disappointed when you're forced to move to Cloud. There isn't an option to have the more expected load leveling views like Chris pointed out. It just dumps all of your overruns to the end and is just like "bad news, this last sprint overruns by something like 400% but I couldn't tell you why or where the problem happens."

We would also love to do this, and are surprised by the pre-set allocation logic for the same reasons as Fabian. 

Roger

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events