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,367,211
Community Members
 
Community Events
168
Community Groups

When do you decide to create a new portfolio plan?

I have created our first plan. As it was our first exercise it has about 700 uncommitted changes.  As I plan out next month am I better off-

a) creating a new plan and include some of the existing epics that overlap and add new ones or 

b) just keep adding  to the existing plan

 

I see the new plan option as cleaner but wondering about the downside

2 comments

Create a new scenario. You can copy your existing scenario with the 700 uncommitted changes, or start fresh with a blank scenario.

I agree with Cameron. Enabling scenarios will give you another playground to work with without impacting the "original" changes. You can choose to Commit from either Scenario as well. 

I would also suggest that you commit the original changes. The phrase I tell folks is, "Commit early; commit often." That way you don't have to review all of them, just the most recent few. 

I consider most changes "safe" when creating a new Plan because you're likely doing the following things: 

  • Tying the Team to the Source (Board, Filter, Project)
  • Adding Estimates or setting a Default Estimate
  • Tweaking The Scheduler (the planning and scheduling algorithm)
  • Creating Initiatives
  • Adding Themes

About halfway down the page on the link below, it will tell you what you're likely committing down to Jira. Of course, you can always select just a few at a time instead of committing all 700+. :)

Cloud - https://confluence.atlassian.com/jiraportfoliocloud/committing-your-plan-changes-828785217.html

Server - https://confluence.atlassian.com/jiraportfolioserver/committing-plan-changes-802170515.html

Comment

Log in or Sign up to comment