Skip to main content

Unified Timeline Gantt Chart

Rollout-Master + V2 Master Plan Comparison​

Created: 2025-12-18 Purpose: Visual reconciliation of two planning timelines Status: DRAFT - Requires stakeholder decision

Timeline Comparison Overview​

Key Findings​

DimensionRollout-MasterV2 Master PlanAlignment
Launch DateMarch 11, 2026September 5, 2026 (Sprint 56)❌ 6 months gap
Days Remaining83 days261 days❌ Misaligned
Current PhaseP0 → Pilot (Dec 24)Sprint 25 of 56⚠️ Partial
Pilot TimelineDec 24 - Feb 18 (8 weeks)Sprint 52-56 (Nov 2026)❌ 10 months gap

Gantt Chart: Rollout-Master Timeline​

Project Span: August 27, 2025 → March 11, 2026 (196 days)

Gantt Chart: V2 Master Plan Timeline​

Project Span: December 16, 2025 → September 5, 2026 (261 days)

Critical Conflict Visualization​

Issue: Two different launch dates exist

Analysis:

  • Rollout-Master: Launch on March 11, 2026 (83 days away)
  • V2 E010 text mentions March 11, 2026 launch
  • V2 Sprint roadmap extends to September 5, 2026 (261 days)
  • Gap: 6 months between stated launch (Mar 11) and V2 completion (Sep 5)

Pilot Phase Comparison​

Issue: Pilot scheduled at different times in two plans

Analysis:

  • Rollout-Master Pilot: Dec 24, 2025 - Feb 18, 2026 (8 weeks)
  • V2 E010 Pilot: Sprint 52-56 (Nov 6, 2026 - Sep 5, 2026)
  • Gap: V2 schedules Pilot 10 months after rollout-master start

Option A: Compress V2 to March 11 Launch

Key Changes:

  1. E001, E002, E010 delivered by March 11 (critical path)
  2. E003-E009 delivered post-launch as monthly releases
  3. Pilot aligned with Sprint 25-28 (Dec 16 - Feb 7)
  4. September 2026 becomes "Platform 2.0" milestone (full autonomy)

Sprint-to-Phase Mapping​

Weeks 1-4: P0 + Pilot Wave 1 (Dec 18 - Jan 21)​

Weeks 5-9: Pilot Wave 2 (Jan 22 - Feb 18)​

Weeks 10-12: GTM Launch (Feb 19 - Mar 11)​

Epic Delivery Timeline​

Pre-Launch Epics (Critical Path)​

Post-Launch Epics (Incremental Delivery)​

Resource Allocation Timeline​

Critical Path Summary​

Path to March 11 Launch (83 Days)​

Week 1 (Dec 18-24): P0 Critical Path

  • Must-complete: Authentication, license management, core stability
  • V2 Sprint 25 start (E001 autonomy begins)
  • Gate: Pilot-ready platform

Week 2-5 (Dec 25 - Jan 21): Pilot Wave 1

  • 5 pilot customers onboarded
  • V2 Sprint 25-26 (E001 complete by Jan 10)
  • V2 Sprint 27 start (E002 Toon UI begins Jan 13)
  • Gate: >60 NPS from first cohort

Week 6-9 (Jan 22 - Feb 18): Pilot Wave 2

  • 5 additional pilot customers
  • V2 Sprint 28-29 (E002 Toon UI in progress)
  • Gate: 10+ pilot customers, >40% conversion commitment

Week 10-11 (Feb 19 - Mar 4): Final Polish

  • Pilot analysis & iteration
  • GTM campaign preparation
  • V2 Sprint 30 (E002 complete, E010 launch prep)
  • Gate: Documentation complete, marketing ready

Week 12 (Mar 5-11): Launch Week

  • Soft launch → Public launch
  • V2 E010 execution
  • Gate: Zero critical vulnerabilities, 99.9% uptime

Decision Matrix​

Timeline: March 11, 2026 launch (83 days)

Changes Required:

  • V2 compressed to Sprint 25-30 (pre-launch)
  • E001, E002, E010 critical path
  • E003-E009 delivered post-launch

Pros:

  • Meets market window (March 11)
  • Aligns with stakeholder expectations
  • Pilot timeline intact

Cons:

  • V2 scope reduced at launch
  • Advanced features deferred

Option B: V2 Authoritative​

Timeline: September 5, 2026 launch (261 days)

Changes Required:

  • Rollout-master extended 6 months
  • Pilot delayed to November 2026
  • Stakeholders informed of delay

Pros:

  • Full V2 scope delivered at launch
  • All 10 epics complete

Cons:

  • 6-month market delay
  • Misses March window
  • Pilot customers waiting 10 months

Option C: Hybrid Approach​

Timeline: March 11 soft launch, September full launch

Implementation:

  • March 11: Core features (E001, E002, E010)
  • Monthly releases (E003-E009)
  • September 5: Platform 2.0 (full autonomy)

Pros:

  • Meets March market window
  • Full V2 scope delivered incrementally
  • Continuous value delivery

Cons:

  • Two launch events to coordinate
  • Ongoing development post-launch

Recommendations​

URGENT (By Dec 20)​

  1. Stakeholder Decision: Choose Option A, B, or C
  2. Update V2 E010: Move Pilot to Sprint 25-29
  3. Communicate Timeline: Unified message to team

HIGH PRIORITY (By Dec 24)​

  1. Create Unified Gantt: Export to project management tool
  2. Reconcile Tasks: Map V2's 17,546 to rollout-master's 1,629
  3. Compress V2: Identify E001-E002 critical path

MEDIUM PRIORITY (By Jan 7)​

  1. Align Sprints: Match V2 sprints to Pilot waves
  2. Define MVP: Document launch scope vs. post-launch
  3. Update Docs: Deprecate conflicting plans

Document Status: DRAFT Requires: Stakeholder decision on Option A/B/C Next Update: Post-decision (by Dec 20) Owner: Hal Casteel, Founder/CEO/CTO

CRITICAL: This unified timeline cannot be finalized until stakeholder decision is made on which plan (rollout-master vs V2) is authoritative for the March 11, 2026 public launch.