Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Your forecast is presented in a table format.

...

The columns are

...

Column

...

Explanation

...

“Epic in progress”, “Epics not yet started”

“Version in progress”, “Versions not yet started”

...

In actual mode - the epics and versions are grouped by their status. The items that are not yet started can be reprioritized. For more details please see Configure the simulation

...

“Epics” or “Versions”

...

This article covers how to read and interact with your forecast for your items in progress.

Jump directly to:

Table of Contents

Reading the forecast

...

Insert excerpt
Step 4: Set forecast parameters
Step 4: Set forecast parameters
nopaneltrue

The Data Columns

Your forecast is a table with 5 columns of information. Here’s what each column tells you

Column

Explanation

Epics (or Versions

Items that you are forecasting. If an epic or version doesn’t have any remaining work to complete then it’s filtered out. Clicking on the

version name or epic

item’s title will take you to either the version’s release page or the epic

it self

itself.

Desired date

This

is what somebody has entered in as a date that they would like to have the version or epic completed. In the case of a version - this is the release date. For epics this is the due date on the epic.

Desired likelihood

The desired likelihood is based on the configured throughput and the order of the versions and epics in the table - what is the likelihood that effort will be completed

value is linked. Click on the link to open the epic or version (release).

Due date (or Release Date)

The due date in your epic or the release date for your version.

Due date likelihood
(or Release date likelihood)

How likely it is that the item will be finished by the desired date.

Items remaining

The number of

regular issues that are not yet completed (in a statuscategory of done) - ie the number of items that should be done in order to complete the

unfinished items associated with your epic or version, excluding subtasks.

This value is linked. Click on the link to see the issue filter showing all items in your epic or version.

Forecasted date

Given the

certainty configured for the simulation, the throughput and the order of the epic or version - what is forecasted date that the epic or version will be completed on.

data configurations and forecast parameters set, you should finish this item on or before this date. (The likelihood of this outcome reflects your chosen confidence level.)

The Color Coding

The row background color for forecasted item rows is set according to the likelihood you’ll meet your due date (epics) or release date (versions) - aka your desired date.

  • Red: < 50% likelihood that you’ll meet your desired date.

  • Yellow: 50-84% likelihood that you’ll meet your desired date

  • White: >=85% likelihood that you’ll meet your desired date OR if you have no desired date set.

Excerpt

Ordering of epics/versions

Until you start rearranging the epics or versions, the Portfolio Forecaster will order them according to their ranking in Jira. If you have modified the ordering and would like to reset back to rank, click the “Reset order” link in the bottom right corner under the forecast table. This option only shows up when you’ve manually changed away from the natural rank order.

Image Added

Next Step

Now that you know how to get a forecast for your epics or versions in progress, you’re ready to jump to simulation mode and play around with some What If? questions! Make sure to become familiar with all of the forecast parameters available when you start viewing items that haven’t yet started!