• Products
  • Documentation
  • Resources

How Ted uses Plans - scenarios and capacity

This page refers to the advanced planning features that are only available as part of Jira Cloud Premium and Enterprise.

We have a separate section for documentation about the project timeline that’s included in Jira. Go to the documentation for the project timeline in Jira.


In the other sections of this guide, we’ve covered all of the tools available to you in your plan. But thanks to its open-ended nature, it can be difficult to string all of these concepts together.

To demonstrate one way that you can combine all the features available to you, let’s look at how planners at Veridian Dynamics use plans.

Meet Ted

Ted leads the ADR Team at Veridian Dynamics. When he looks at the workload for the next year, he sees that his team is overwhelmed and requests the budget for another developer. To strengthen his case, Ted uses a plan to demonstrate the positive impact another developer would have on the team’s development timelines and help them achieve their goals.

How Ted sets up his plan

Ted creates a plan creatively named “Ted’s Plan”, and uses the ADR Board as his issue source. Next, he adds the ADR Team in the Teams menu, and associates it with the ADR Board:

Ted enables scenarios in his plan, then creates a new one in Advanced Roadmaps

He can now begin to plan.

How Ted plans work for his team

In order to prove how another developer will help his timelines, Ted needs to illustrate the current expected deliverable dates. He estimates all of the issues on his timeline to the best of his ability. A lot of his work stretches far into the future, but he’s able to roughly state how long he thinks each individual task will take.

Once the issues are estimated, he groups issues on his timeline by Team and sets his plan to schedule issues based on their sprint dates:

In order to view capacity on his timeline, Ted groups his Advanced Roadmaps plan by teams

Then, using the capacity planning tool, he assigns work to each sprint to determine how many iterations of work his current team has on their plate, based on their current capacity of 30 story points:

This is what Ted's plan currently looks like in Advanced Roadmaps

By his current estimations, his team will take seven iterations to finish their current project. From here, he repeats the process with the next project, building his rough plan for the year.

Next, Ted needs to make a scenario where his team has a higher velocity. He enables scenarios in his plan, and names this plan Current team:

In order to compare his plans, Ted enables scenario planning in Advanced Roadmaps

He then copies his existing scenario into his new scenario and names it New hire:

Ted creates a second scenario in Advanced Roadmaps

In his new scenario, Ted increases the sprint capacity to reflect the addition of a new developer, and then adjusts his issue assignments based on this new bandwidth:

With his new capacity, Ted can see what his project might look like in Advanced Roadmaps

When he’s done, Ted can now show how another developer will help his team. With a new hire, they’ll finish their first project almost a month ahead of their current projections. And that through the course of a year, adding another developer will free up six weeks of extra time.

When Ted presents this to his boss, he switches between the two scenarios to contrast the two timelines.

Other examples:

How Veronica uses Plans - cross-project planning

Further reading:

Learn more about issue sources

Learn more about scenario planning

Learn more about capacity and velocity


Still need help?

The Atlassian Community is here for you.