User guide

1. The PI at a glance

In the centre, the train's teams; around them, their objectives, then their epics. The colours tell the state of the stories: green done, orange in progress, blue to do, red postponed.

The top bar counts the stories, and the share of them attached to an objective. On the right, the PI's objectives with their progress.

See it in the example

2. A team's objectives

A click on a team shows its objectives, each with its progress.

A red objective marked “No US yet” has no work described yet: here, Gift cards. It always stays in view, so that it gets discussed with the team's PO before the review.

See it in the example

3. One objective in detail

A click on the objective shows its epics, then their stories. The panel gives, for each epic, how many stories are done.

See it in the example

4. What is still missing

The “To clean up” tab gathers what skews the review, among which:

• epics with no objective: work that serves no objective of the PI;
• objectives with no US: commitments with no work described.

A click on a line leads to it in the sunburst.

See it in the example

1. The dependencies between teams

In the centre of the sunburst, a ribbon joins two teams whose stories are linked. “Blocking only”, under the sunburst, keeps the links that block.

A click on a ribbon lists its links in the panel: who blocks whom, and under which objective. Here, Data blocks two stories of Payments.

See it in the example

2. The train's planning conflicts

A blocking link is in conflict when the blocker will not come in time:

• it is planned in a sprint that starts after the one of the story it blocks;
• it is in no sprint of the PI;
• it is postponed.

The conflicts come first in the “To clean up” tab. Each line names the blocker, its team and both sprints: enough to prepare the sync between teams.

See it in the example

3. The conflict, seen from both sides

A click on a line opens the story's card. The conflict reads there in a frame, from each team's side:

• at Data, DATA-246 “blocks PAY-160, which needs it in Sprint 64”;
• at Payments, PAY-160 is blocked by a story planned in Sprint 65, after it.

Both POs see the same conflict: theirs to bring the blocker forward or move the story.

See it in the example

1. The team's “To clean up” tab

A click on your team, then on the “To clean up” tab: everything that calls for an action in Jira, by motif, with their count on the tab.

See it in the example

2. The stories left behind

A story out of sprint was in a sprint that closed, and no sprint has taken it since: its card says so. To plan again, or to postpone if it will not be done in the PI.

A story carried over twice or more moves from sprint to sprint without ending: often too big, or blocked.

See it in the example

3. What is attached to nothing

• the stories with no epic: to file in an epic;
• the epics with no objective: to attach to an objective of the PI, or to own as work outside the objectives;
• the objectives with no US: to describe with at least one story.

Once fixed in Jira, the motif goes away at the next refresh.

See it in the example

1. Find it

The search, on the left, finds a story, an epic or an objective by its title. A click on the result opens its epic and selects the story.

See it in the example

2. Read its card

• Sprints: the story's path from sprint to sprint, and its carry-overs. Here, two: Sprint 62, then 63, then 64.
• PI timeline: its statuses over time, across the PI's sprints, then the same detail as a table. Here, to do for 16 days, then in progress for 35.
• Dependencies: what it waits for. Here, DATA-246, planned one sprint too late.

The ↗ arrow opens the story in Jira, to act on it.

See it in the example

1. Start the timelapse

The Timelapse button, on the left, opens a bar under the sunburst. Helioviz reads the stories' status history from Jira, then replays the PI.

▶ starts on the PI's first day and moves on to today. The slider takes you to a given date.

Try it in the example

2. What it tells

• Blue that stays late: work that started late in the PI.
• Orange that lingers: too much work in progress at once.
• Red that shows up: postponed stories, and when.

Another click on Timelapse goes back to today.