---
title: "Live Roadmap"
slug: delivery-live-roadmap
section: Delivery
status: active
description: "Live Roadmap is the shared recovery and planning workspace within Delivery."
last-updated: 2026-10-07
---

# Live Roadmap

Live Roadmap is the shared recovery and planning workspace within Delivery.
Open /docs/delivery-live-roadmap for the interactive Executive, Delivery and
Product + Engineering views.

Once business direction is imported, each perspective opens the same compact
five-quarter release timeline, even before capabilities are selected or forecasts
are validated. Independent release groups are initially unsaved proposals
derived from real scope. Create, reorder, split, combine and edit groups; move
scope between releases, plan incremental portions, undo local changes and
save separate audited release-plan versions. Release edits never rewrite
approved business targets or automatically write to Asana. Executive focuses
on priorities, source targets and exposure; Delivery on owners, dependencies
and execution; Product + Engineering on application contributions and readiness.
Execution completion, validation and production evidence remain distinct.
Unknown execution progress is unknown, not zero. Production status requires
recorded validation and release evidence, not just completed tasks.
Q4 2026 through Q4 2027 are visible together. Quarter, Month and Year labels
change the axis without inventing month-level precision. Bright workstream colors
identify work, not delivery health. Proposed quarter allocations, approved-target
diamonds, observed Asana dates and validated forecasts are separate markings.
Expand workstreams and releases to inspect scope or use the existing release
builder. Executive hides editing by default; Delivery emphasizes owners and
observed execution; Product + Engineering emphasizes readiness and contributions.
Discovery and
directional work stay distinct from delivery. Inspect items for linked
capabilities, dependencies, Asana records and source evidence.

Capabilities, Planning & capacity, Sources & recovery, Asana alignment and
History remain supporting tools. Observed execution timelines and advanced
planning remain available separately. Missing inputs never hide the imported
roadmap. Source-row counts are not counts of accepted business outcomes.

Create capabilities or recover live Asana projects, import historical XLSX/CSV/TSV
intent, validate source links and remaining demand, enter weekly capacity, then
calculate forecasts or isolated scenarios. Missing inputs remain explicit.

Asana plan recovery reads the designated Q4 Roadmap Delivery portfolio and its
nested tracks. Historical project/task dates and source links stay separate
from targets and approvals. Repeated recovery preserves planning edits; task
evidence refresh runs in bounded batches without writing back to Asana.

Business targets, approved baselines, calculated forecasts and evidenced actuals
are separate. Asana is read-only. Production planning and evidence APIs reuse
the existing Nexus signed-in session; no separate Roadmap login is needed.
Baseline approval requires an explicit business-approver grant. Development
follows Nexus's preview bypass in a separate draft workspace that cannot
approve commitments. No private planning records appear in this
public guide. Existing Delivery reporting and exports are preserved.