The Portfolio report is most commonly used for an at-a-glance view across teams and strategic initiatives to see what’s on track, what needs your attention and improve alignment with product stakeholders.
| Table of Contents |
|---|
...
Understanding the Report
The report enables engineering and product leaders easily visualize actual to forecast delivery dates and trends for key roadmap items and deliverables. With this insight, leaders gain data-driven insight where the teams need support and effectively communicate with fellow stakeholders to manage expectations and prioritize initiatives.
...
Progress:
In count mode, the bar will show complete and incomplete segments.
In story point mode, the bar will split into three segments.
Completed, Incomplete but Estimated, Incomplete and Unestimated.
Status
Populated by the equivalent status field for card in Jira or Azure DevOps (ADO)
Commits:
Shows code commit activity over the last seven days.
Velocity:
Shows item completion activity over the last seven days.
Scope Remaining:
Shows the change in total remaining scope over the last seven weeks.
Target End Date:
Populated by the equivalent due date field (Jira) or Target Date field (ADO)
Populating this date changes how forecasted end date displays relative to this date.
Forecast:
Displays the Allstacks forecasted end date based our proprietary algorithms utilizing issue assignees, velocity and cycle time. If you have a target end date, it will display if we are forecasting an early, on time, or late delivery.
Get Started: Add Milestones
To add the deliverable work that you and your team care about to the Portfolio Report, click the “Add Milestones” button on the top-right of the screen.
...
Note: The Portfolio Report is saved at the team-level. Any edits you make will be reflected for all users accessing the team workspace.
...
Configure Estimation Method and Sorting
Estimation Method:
Until edited by the user, all milestones will default to the most specific estimation method we can detect.
...