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” | In simulation mode - this shows the epics or versions that are forecasted. If an epic or version doesn’t have any work to complete then it’s filtered out. Clicking on the version name or epic title will take you to either the version’s release page or the epic it self. |
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 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 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. |