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,558,435
Community Members
 
Community Events
184
Community Groups

managing capacity in 2 teams but 1 sprint

I'd really like to use the new Advanced Roadmaps however, i'm having trouble figuring out how to best model our environment.

 

First of all, we operate with a 4 week sprint and then a 1 week gap week... which basically allows us to do some clean up, individual learning, experimentation, retro, and plan for the next sprint.

How do you best represent a cycle like this in advanced portfolio? There doesn't seem to be a way to have varying length sprints or way to have a gap between sprint dates? Typically we basically have 4 week sprint and a 1 week sprint.

 

We also have both engineers and developers and estimation/capacity is often tied to those disciplines. Often we need both devs and engineers on an issue. How do you best represent this? Separate them into different teams and 1 issue for each team?

 

Our team has multiple part time schedules on it and some that very sprint by sprint. How do you best account for this sort of variability within the capacity? It almost would be helpful to decide what the capacity is for each sprint for me.

 

It's working okay for us tracking outside of jira in just a simple spreadsheet but have issues with the longer term planning types of things (tracking dependencies, releases, etc).

 

Any suggestions on how best to model an environment like this? or is roadmaps just not a good fit?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events