Charts & Trends

Coaching charts for the current PI plus sprint- and iteration-scoped views of how the team is delivering today. Click a small card to swap it into the large view. Reach for the chart that fits the conversation you're having — you don't need to look at every one every time.

The Charts view — velocity with rolling average

Delivery & flow

Epic Progress — per-epic Done / Total story-point bars across the PI, with an overall donut and a By Type breakdown. The Epic Growth toggle reveals what was added or removed mid-PI.
Velocity — story points completed per sprint (Scrum) or iteration (Kanban). The dashed line is the rolling average across delivered iterations only, so unstarted ones don’t drag it down.
Throughput — items finished per sprint/iteration. Watch for sudden drops (blockers, scope shifts) and sustained climbs (real improvement).
Predictability (Scrum) — completed-vs-committed ratio per sprint. Healthy bands sit between 80–120%; wide swings suggest over-committing.

Cycle time & WIP

Cycle Time Scattergram — each dot is a completed ticket, plotted by finish date and days taken. Dots above the trendline are the outliers worth a retro.
Cycle Time (Trend) — average cycle time per sprint/iteration. A slowly rising line often means WIP creep — pair it with the WIP chart.
Work In Progress — average concurrent active items. Keep it near the team’s WIP target; too high correlates with longer cycle time and more context-switching.

Burndown, burnup & CFD

Sprint Burndown / Burnup (Scrum) — remaining SP vs an ideal line, and cumulative done vs total scope. A jumping scope line is mid-sprint scope creep.
Sprint / Iteration CFD — Cumulative Flow Diagram: stacked To Do / In Progress / Done bands. A widening In Progress band means work is piling up — ease off starting new things.
Aging WIP (Kanban) — tier counts (green / orange / red) for in-flight tickets vs the team SLE, plus a per-ticket bar sorted oldest-first. Anything past the SLE marker is a coaching conversation.

PI-level views

PI Burndown, PI Burnup, and PI CFD extend the same ideas across the whole increment, with iteration boundaries marked at end-of-iteration — useful for retrospectives spanning the PI.

PI Forecast (Monte Carlo)

The Forecast card leads with a scope-decision row, then Monte Carlo percentiles, then a calendar timeline.

Tile	Meaning
Scope	Total SP committed to the PI now, with the delta since PI start.
Projected Delivery	SP the team is forecast to deliver by PI end at high (P85) confidence. Can exceed Scope when the team has slack — the gap is buffer.
Action	"On track · +N SP buffer" when projected ≥ scope, otherwise "Descope N SP to hit PI end".
On-time %	Probability the team finishes inside the PI's sprint budget.
P50 / P85 / P95	Weeks by which 50% / 85% / 95% of simulated trials finish.

The simulator uses average velocity over the last 5 non-IP sprints, the standard error of the mean as its variance (so one off sprint doesn’t drive the forecast to doomsday), and a sprint-count time budget. With fewer than three completed sprints it returns “insufficient history” — Monte Carlo needs at least three data points to estimate variance honestly.

Hover any point or bar for the exact value.