Initiativen & Phasen

Den langen Bogen Ihres Projekts planen

Gruppieren Sie zusammenhängende Arbeit in strategische Initiativen und unterteilen Sie diese in zeitlich begrenzte Phasen mit Ergebnissen und Verantwortlichen.

Zugang anfragen
Project planning hierarchy
📋 Project Spec — "Build the checkout platform" approved
🚀 Initiative — "v1: Core checkout flow" active
Phase 1 — "Auth + cart" completed
Phase 2 — "Payment integration" active
Phase 3 — "Order history + emails" planning
🚀 Initiative — "v2: Mobile checkout" planning

Two Layers of Planning

I

Initiative

A major strategic effort spanning multiple phases. Examples: "Build the checkout flow", "Migrate to v2 architecture", "SOC2 compliance sprint".

  • ✓ Links to the project spec that spawned it
  • ✓ Carries its own success criteria and out-of-scope list
  • ✓ Has a target date and owner
  • ✓ Status: planning → active → completed
P

Phase

A time-bounded slice of work within an initiative. Examples: "v1.0 — Core auth", "Sprint 3 — Payments", "Beta release".

  • ✓ Ordered within its initiative (drag-to-reorder)
  • ✓ Lists deliverables and linked goal IDs
  • ✓ Has start date, target date, and owner
  • ✓ Phase completion updates initiative progress

Full Traceability

Every piece of work traces back to a strategic decision. When you ask "why did we build this?", the answer is always one click away.

Project Spec
What to build, for whom, under what constraints
Initiative
A major effort aligned to the spec
Phase
A time-bounded slice of the initiative
Goal
A measurable outcome the phase delivers
Job
The actual work executed by expert agents

Von der Spezifikation zur Lieferung

Projektspezifikationen speisen Initiativen, Initiativen formen Phasen, Phasen treiben Jobs an.

Frühzugang anfragen