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,560,497
Community Members
 
Community Events
185
Community Groups

Kanban Capacity Planning & Scenarios in Advanced Roadmaps

  1. My teams use a Kanban pull system and don't plan work in sprints.  Also, they estimate in hours and not story points.  I understand that teams can be setup as Kanban or Scrum.  Is it required to schedule work in sprints in order to plan capacity using Advanced Roadmaps?
  2. I also understand the Scenarios provide a sandbox for planning.  I tested moving Ranks for Initiatives in a Scenario and saved the changes.  This changed Ranks on all of my Scenarios and Roadmaps.  Is the theory of using Scenarios that you can play in the sandbox and as long as changes are discarded, Scenarios and Roadmaps don't get impacted, but if changes are saved they will be impacted?

1 answer

I face the same problem. It looks like that scenarios work with the same sources, filters and view settings and if you change that in one scenario, it automatically changes in all other scenarios, which reduces the added value of the scenarios.


I hope that there are ways to differentiate other than making another plan. 


Saving the view under a different name (for each scenario a dedicated view, will solve part of the problem as I want to remove from the plan issues that are not relevant for the different scenarios.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events