FAiS PortfolioSign in to see the portfolio
Use your Automus Microsoft account. Access is limited to the FAiS team.
| Product | Against its own history | Built | Current sprint | Next two sprints | Risks |
|---|
Each product is compared with itself. Pace so far: points done or ready to deploy by this day of the sprint, against the same day in its past sprints. Expected finish: the plan times the share of its plan it usually completes. A product needs two closed sprints for a pace verdict. The Built bars share one scale, so the biggest product has the longest bar. Click a row to open that product.
How much of each plan gets done
The grey line traces what each sprint planned and the navy line what it finished inside the sprint; the shaded gap is work that slipped. Percent is the share finished. For the running sprint, the dashed blue line and pale bar show where it should land at that product's usual completion range. Each product has its own scale so small teams stay readable; the percentages compare across rows. History counts only items still in the sprint when it closed.
Release dates and milestones: set fix versions in Jira, or link the delivery plan, and they will show here.
Budget, cost and headcount plans live outside Jira, so they are not shown.
Top risks and decisions needed
Written from the morning pull.Changed since the full pull
Risks and asks
Written from the morning pull.Plan the next two sprints
Every level folds: initiative, then epic, then story. Drag a whole initiative, a whole epic or one story into the other sprint or the backlog, or use the switch at the end of its row. Auto-fill keeps what Jira already has in these sprints, then fills Sprint by Sprint to capacity in priority order, skipping blocked and unpointed work. Type points on unpointed items to size them.
