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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Remaining estimates spread evenly across start date/end date in Adv Roadmaps?

We are working to use Advanced Roadmaps for our teams capacity planning, but we have monthly allocated support hours spread across an annual (or multi-month) term that we have set up as projects in Jira.  The way I have seen Adv Roadmaps calculate available capacity is use up the teams capacity for the project ending soonest and pushing out the remaining estimate on all projects that end after, basically appearing that we have enough capacity until we look a year or so out at the latest ending project.  I was curious if anyone has found a way to have advanced roadmaps spread out the estimate evenly across the length of the project so we can understand what we need to delivery on on monthly support commitments.  TIA!



1 answer

1 vote
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 03, 2021

Hi @Jennifer Mancke,

Advanced roadmaps (and roadmaps in general) is built around the principles of the iron triangle of planning, where you have a certain scope, one or more teams to deliver and your target dates over time.

Support work is not well suited to be managed through a roadmap, as it is unplanned work by nature. Incidents are unpredictable as to when they happen, they are usually solved rather than estimated and - as such - virtually unplannable.

And still, many organisations and teams are working in a hybrid mode, partially doing project work and partially delivering support. And that is often an interesting approach, though often the support workload puts a heavy strain on delivering new value.

It may be a good idea - if you don't do this already - to look at your team's capacity and divide it across project and support work. Remove the support work from your average team capacity. If - a totally random example - your team spends on average 40% of its time on support and 60% on projects, reduce your team capacity by 40% in the plan and only pull your project work in there - not the support.

Due to the unpredictable nature of support, this will obviously vary over time. But the better your high level metrics on this distribution of work, the more reliable your capacity / forecasting will become.

I know this is not a technical answer about the tools, but I still hope it helps you forward in your approach. 

Thanks Walter.  Yeah, we have already accommodated for the split between project and support work.  

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events