Plan & Gantt

The plan, week by week

Every task on one chart, the steps of a sprint, and the dates that matter.
The plan

January to launch, on one chart

Each bar fills as its work is done. The red line is today.
Task
JanFebMarAprMayJunJulAugSepOct
Customer interviewsDone · Priya
100%
Problem statementDone · Priya
Design systemDone · Leo
100%
Prototype and testsDone · Leo
100%
Platform and APIIn progress · Sam
80%
Web appIn progress · Sam
62%
Mobile appsIn progress · Ana
40%
Security reviewBlocked · Ana
20%
Closed betaNext · Priya
0%
Launch campaignPlanned · Mia
0%
Public launchPlanned · Everyone
How we work

The same five steps, every sprint

Planned on Monday, shown to customers on the second Friday.
  1. Monday

    Plan

    Pick the work and size it.

  2. Days 2-8

    Build

    Small changes, reviewed the same day.

  3. Day 9

    Test

    Automated first, then by hand.

  4. Day 10

    Show

    A demo to five customers.

  5. Day 10

    Learn

    What to keep, what to change.

Milestones

The dates that matter

Owned by one person each, reviewed every Friday.
Updated every Friday
MilestoneOwnerDueStatus
Problem statement signed offPriya14 FebDone
Design system 1.0Leo28 MarDone
API feature-completeSam30 JunIn progress
Security review passedAna18 JulBlocked - waiting on audit
Closed beta opensPriya5 AugNext
Public launchEveryone15 OctPlanned
Risks

What could slow us down

Every risk has an owner and a plan. We say so here the week one changes.
The security audit runs late
The audit firm has two weeks' slack built in; the beta can open to fifty customers first if it slips.
Mobile app review takes longer
Both apps go to review a month early, with a web fallback for anyone waiting.
The beta finds a big problem
That is what the beta is for: six weeks are held between beta and launch.

aurora·roadmap

Project Aurora, built in the open: where it is, what is next, and what changed.
The roadmap
© 2026 Metro Page Builder - MixAgile.com · Project Aurora is an invented project