Use Cases

Gantt Charts

Use case: a portfolio Gantt that shows three teams' work, their cross-team dependencies and a fixed launch date on one timeline, with a plan-of-record scenario to measure drift against.

The situation. A product launch depends on three teams: Platform (API), Mobile, and Go-to-Market. Each team plans in its own boards and sprints and each is confident about its own dates. Nobody can see whether the dates line up, and the launch date is contractual.

What you want. One timeline that shows all three teams' work, the dependencies between them, the launch as a fixed point, and a way to answer "if the API slips, what breaks?" before it happens.

Build the chart

  1. In Track Progress, click + Create then Gantt Chart. Name it after the launch, put it in a Programs Gantt group, and describe who owns it. See Create New Gantt.
  2. Add three initiatives, one per team, each with its own color. Initiative dates roll up from the work inside, so you never type them.
  3. Click Import and add each team's launch workstream to its initiative. Importing the workstream rather than individual items means new stories the teams add later appear automatically. Imported items from integrations show an import badge and behave like any other. See Add to Gantt.
  4. Add a Milestone for the launch date.
  5. Fix every Date missing cell: click the bar to accept the inferred dates, or ask the team for real ones. For workstreams whose children spill outside them, Shift + click the date cell to snap to the children.

Wire the dependencies

  1. Hover the API workstream's bar and drag from its connector to the Mobile workstream; choose Dependency. Do the same from Mobile to the GTM workstream, and from GTM to the launch milestone.
  2. Add Related links for connections that are informational only, such as the marketing site redesign that shares a designer but does not block anything.
  3. Open the Dependency Graph from any item to confirm the chain reads API → Mobile → GTM → Launch.

The chart refuses loops and ancestor/descendant links, so what you can draw is what can actually be scheduled.

Read it in each team's calendar

  • Click Snap to cycles and select the Platform team's sprint folder. Mobile can now see which Platform sprint their blocker ends in. Switch the folder to the GTM program-increment folder to read the same chart in PI terms.
  • Save a view per team: filter to the team, set the zoom and expanded rows they like, and share the link. See Viewing Gantt Charts.
  • Set Options → Show Bar Progress By to Point estimate if the teams size in points, so the bars fill by effort rather than by story count.

Rehearse the slip

  1. Clear filters, expand the chart, and click Scenarios. Start a scenario named Plan of record and save it without moving anything. This is your baseline.
  2. Start a second scenario, API slips 2 weeks. Switch to Linked mode (Shift + M) and drag the API workstream's due date two weeks right. Mobile, GTM and the launch milestone move with it on screen; nothing is written to the items.
  3. Click Scenarios to review the Recorded updates, then Save scenario. The chart shows the saved scenario as a baseline with the day deltas in the scenario columns.
  4. Decide. If the launch cannot move, the question becomes which Mobile scope to cut; if it can, make the real moves on the live chart in Linked mode and record a new Plan of record.

See Scenario Planning and Link Mode.

What you end up with

  • One chart, three audiences, each with a saved view.
  • Dependencies that are real relationships on the items, visible in the item workspace and the Items Table as well as on the chart.
  • A launch milestone that turns a vague slip into a specific crossed line.
  • A dated baseline to measure drift against at every review.