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

Portfolio scenarios - changing team velocity to express pessimistic, most likely to optimistic


The schedule configuration for a Portfolio Plan, where one defines Sprint length, Default velocity appear to be sticky for the plan.

So one can't establish scenarios where one can set (pessimistic, most likely, optimistic) velocity to view the scenario for the plan.

Is there a way to do this without creating separate plans?

Why are parameters like sprint cadance and team/group velocity sticky to the plan?

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 11, 2018

Hi @Tarang,

Yes this is possible with Portfolio for Jira. 

If you enable the multiple scenarios feature you could then create 3 scenarios "pessimistic, most likely, optimistic". You would only need one plan to do this.

Then, you could adjust the sprint velocities for each scenario and compare them.

Hope this helps


That’s what I thought should be possible alas that’s not what actually occurs.

i did create the 3 scenarios and set the “Default velocity” for each, however when we look at the plan and schedule view we do not see the effect take place.

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 11, 2018

Ah, sorry our instructions weren't clear. For each scenario you'll need to set the velocity in the "Teams" tab.

"Default velocity" is a plan configuration setting, so it affects the entire plan (including every scenario). 

How so as the “Teams” tab intuitively appears to me to correspond to the Plan and not to a “scenario”? Though I see one can assert a number of changes in the scenario, including team capacity as much as backlog item priority order.

In any case I did this and I do not see any changes directly as a result of this as i imagined to show up on viewing “Scope” by “Capacity”.  I see one has to trigger “Calculate” for the action to take effect, which I guess is a trigger to invoke when number of changes have been applied.

okay so that is all cool except:

Now the question is why would the capacity values for each sprint not be close to the Teams velocity?

For instance if the optimistic is set to 27  story points, why are most sprints in the plan showing to be between 6 and 11 story points?


I suspect the reason why portfolio plan viewed in ‘capacity’ shows partial fills on sprints is

  1. number of teams are identified with the backlog 
  2. team is solely defined with 1 skill (dev)

There is no need to make some complicated algorithm to establish this.

It should work with the Simplest assumption that all the backlog is fulfilled by the team(s) based on team velocity.  It should not be making any assumptions that are not explicitly configurable. Such as factoring subjective settings of skills on the team.  Assume the team will figure it out is they don’t have readily available skills as good news is human beings are a learning machine!

Why make it so complicated when simplest ideas will serve?

Like David Hiatt likes this

THIS! > "It should not be making any assumptions that are not explicitly configurable."

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events