Gantt Charts

Scenario Planning

Record what-if date changes on a Gantt chart without touching real items, save them as a named scenario, and overlay any saved scenario as a baseline to see exactly which dates moved and by how many days.

A scenario is a rehearsal. You drag bars around to answer a question like what if the API work slips two weeks? and, while you are recording, none of those moves reach the real items. When you save, DevStride stores a snapshot of the chart's dates under a name. Later you can lay that snapshot over the live chart and see, item by item, where the plan drifted.

Scenarios live on a single chart. You need edit rights on the chart to record, save, rename or delete them (MANAGE_OWN_GANTTS for your charts, MANAGE_ALL_GANTTS for others'). Anyone who can open the chart can view a scenario as a baseline.

The two modes

ModeWhat you seeWhat is written
RecordingThe Scenarios button pulses amber. Date moves show immediately on the chart. Three extra columns show each row's Original start date, Original due date and Original duration; changed rows are highlighted.Nothing, until you save. Recorded moves live in your browser.
BaselineThe Scenarios button turns blue and a badge with the scenario name appears above the table. Grey shadow bars show where items were in the scenario. Three extra columns show Scenario start date, Scenario due date and Scenario duration with the difference in days.Nothing. Baseline is read-only.

Record a new scenario

  1. Clear any filters. Scenarios is disabled while filters are applied, because the snapshot has to cover the whole chart.
  2. Expand the rows you want captured. The snapshot includes every expanded row that has valid dates, whether or not you moved it.
  3. Click Scenarios. Under New scenario, type a name of at least 2 characters (the placeholder suggests Eg. Optimistic estimate) and click Start. Press N to jump to that field.
  4. Read the Scenario recording mode activated dialog and click Sounds good.
  5. Move bars, resize them, edit dates in the table, or set dates with Shift + click. Everything you do is recorded; nothing is saved to the items. Linked and Unlinked mode still apply, so a due-date move in Linked mode records the cascade too. The table's Progress, Cycle / Board and Relationships cells, and any Items Table or custom-field columns you have added (such as Assignee or Status), are read-only while you record, since those edits would change the real items. The row menu's entries that change items are greyed out too (Not available while a scenario is being recorded).
  6. Click Scenarios at any time to open Scenario Information: the scenario name and the Recorded updates (newest first), each with the item, the new start or end date, and the mode it was recorded in. Undo removes a single recorded change.
  7. Finish with one of the two buttons beside Scenarios:
    • Save scenario (check). The Save scenario dialog reminds you that a date snapshot of all the expanded items with valid dates will be saved as well. Click Save. The scenario is created and immediately applied as a baseline so you can see the deltas.
    • Cancel and discard scenario (x). Confirm with Cancel recording, or Continue recording to go back.

View a scenario as a baseline

  1. Click Scenarios and click a scenario in the list. Each shows its Last updated time.
  2. The chart overlays the scenario: a grey shadow bar labeled with the scenario name appears under every item whose dates differ, connected to the live bar. Items whose dates match show no shadow.
  3. Read the three scenario columns. A value like 12 Jun 25 (+5) means the scenario had this item five days later than it is now. Green means the live date matches the scenario; red means it has moved.
  4. To leave baseline view, click the scenario again (it toggles), use Clear in the dialog, or click the x on the scenario badge above the table.

Baseline view is part of a saved view, so you can give stakeholders a link that opens the chart with a specific scenario overlaid. See Viewing Gantt Charts.

Edit, rename or delete a scenario

In the Scenarios dialog each row has three controls:

ControlShortcutDoes
Record (dot)RStarts recording into this scenario. Save replaces its snapshot with the new one; the scenario is then applied as baseline.
Rename (pencil)EEdits the name inline. Enter saves, Esc cancels. Names need 2 characters or more.
Delete (trash)DeleteRemoves the scenario after you confirm Delete. This cannot be undone. If it was the active baseline or recording, the chart returns to its normal state.

Done closes the dialog.

Technique: run a what-if in ten minutes

Here is the pattern most teams settle on.

  1. Capture the plan of record first. Start a scenario called Plan of record, Q3, move nothing, and save. You now have a baseline to compare against later, which classic Gantt tools would call the baseline plan.
  2. Ask one question per scenario. API slips 2 weeks, Drop feature X, Add a contractor to search. One change per recording keeps the deltas readable.
  3. Record in Linked mode when the question is about knock-on effects. The cascade shows you what else moves; the Scenario Information list is the audit trail.
  4. Compare with the live chart. Apply the scenario as baseline, scan the red cells in Scenario due date, and sort out which slips cross a milestone.
  5. Commit deliberately. Scenarios never change items. If the team agrees to the new dates, make the real moves on the live chart (Linked mode will do the cascade for you), then record Plan of record, revised so the next comparison starts from the right place.