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,464,714
Community Members
 
Community Events
176
Community Groups

Managing capacity with Advanced Roadmaps and Cross Project Releases

Edited
Rob Horan Community Leader Mar 07, 2022

I am having a very hard time trying to find some best practices and getting started guides for Advanced Roadmaps, and there is a particular solution I am trying to devise.

Assume a scenario in which Jira has been configured with projects based on functional teams.

For releases, an Epic is created, composed of issues from various projects.  Each project has its own sprints.  The sprints across projects are essentially in alignment, but they are not the same in terms of name.

There may be multiple Epics completed in a period of time, and so these are sometimes, but not always sequential or dependent.

High level planning takes place using a plan containing only Epics, but this does not allow for capacity planning.  Teams are not yet in use, nor are versions/releases in Jira, especially since these releases span multiple projects.

Assume each functional group has a set of members, and members from each group are split, some working on one Epics while others work on another.

Multiple Epics may be in progress simultaneously.

Is it possible to create teams in Avanced Roadmaps to track capacity in a scenario like this?

For Example, Epic A may need half of the IT team, and Epic B might need the other half.  Is there any way to track capacity across these epics for this team? 

Is there a way to manage capacity across epics where team members are shared across epics?  Can capacity planning in Advanced Roadmaps be used to schedule work on one Epic when the need for a functional group is done on another Epic?

1 answer

Hi @Rob Horan 

Answering your question: "For Example, Epic A may need half of the IT team, and Epic B might need the other half.  Is there any way to track capacity across these epics for this team?
Is there a way to manage capacity across epics where team members are shared across epics?" the answer is probably no. 
For example, ActivityTimeline resource planning plugin has a Team panel where you can add an Epic and calculate the workload and availability. Or there are a possibility to book a time in percentage for a Teams.  
But I think you need to operate with scheduled tasks on a team nor a whole epic. It will be much easier to find a proper plugin.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events