Phased Roadmap

Attribute	Value
Project	[Project Name]
Version	0.1
Status	Draft
Owner	Product Owner

Table of Contents

• Planning Principles
• Phase Overview
• Phase -1 (Validation & Prototyping)
• Phase 0 (Foundation & Engineering Readiness)
• MVP Phase
• Phase 1 (Enhancement)
• Phase 2 (Future)
• Feature Traceability Matrix
• Risks and Blockers

Planning Principles

[State the rules that govern how work is sequenced, e.g.:]

• Validate the user experience before scaling engineering effort.
• Foundation work (repo, CI/CD, environments) precedes feature work.
• Only Must priorities enter the MVP phase; Should/Could items are deferred consciously.
• Every phase has explicit acceptance criteria before the next phase starts.

Phase Overview

Phase	Name	Objective	Status	Target Window	Execution Mode
Phase -1	Validation & Prototyping	[Objective]	Draft	[e.g. Weeks 1–2]	[Parallel/Serial]
Phase 0	Foundation & Engineering Readiness	[Objective]	Draft	[e.g. Weeks 2–4]	[Parallel/Serial]
MVP	[MVP name]	[Objective]	Draft	[e.g. Weeks 4–10]	Serial
Phase 1	Enhancement	[Objective]	Draft	[Post-MVP]	Serial
Phase 2	Future	[Objective]	Draft	[Undefined]	Deferred

---

Phase -1 (Validation & Prototyping)

Goals

• [Goal 1, e.g. validate core user flows with a clickable prototype.]
• [Goal 2]

Prioritized Tasks

Priority	Task	Owner	Estimate	Deliverable
Must	[Task]	[Role]	[e.g. 2d]	[Deliverable]

Key Deliverables

• [Deliverable 1, e.g. approved prototype brief and design direction.]
• [Deliverable 2]

Acceptance Criteria

• [Criterion 1]
• [Criterion 2]

Dependencies and Blockers

• Blocks: [What cannot start until this phase completes.]
• Requires: [Inputs this phase needs.]
• Can Run in Parallel With: [Phases that may overlap.]
• Coordination Points: [Handoffs that need explicit sync.]

---

Phase 0 (Foundation & Engineering Readiness)

Goals

• [Goal 1, e.g. repository structure, CI/CD pipeline, and development environment ready.]
• [Goal 2]

Prioritized Tasks

Priority	Task	Owner	Estimate	Deliverable
Must	[Task]	[Role]	[Estimate]	[Deliverable]

Key Deliverables

• [Deliverable 1]
• [Deliverable 2]

Acceptance Criteria

• [Criterion 1]
• [Criterion 2]

Dependencies and Blockers

• Blocks: [What cannot start until this phase completes.]
• Requires: [Inputs this phase needs.]
• Can Run in Parallel With: [Phases that may overlap.]
• Coordination Points: [Handoffs that need explicit sync.]

---

MVP Phase

Goals

• [Goal 1]

Prioritized Epics

Epics are tracked in your work-item tracker (e.g. Jira). Document the epic/story conventions used by your team in your tracker setup.

Priority	Epic	Linked Feature(s)	Linked Requirements	Owner
Must	[EPIC-x]	[F-xxx]	[FR-xxx-xx]	[Role]

Key Deliverables

• [Deliverable 1]

Acceptance Criteria

• [Criterion 1]

Prerequisites

• [Prerequisite 1, e.g. Phase 0 acceptance criteria met.]

---

Phase 1 (Enhancement)

Goals

• [Goal 1]

Prioritized Epics

Priority	Epic	Linked Feature(s)	Linked Requirements	Owner
Should	[EPIC-x]	[F-xxx]	[FR-xxx-xx]	[Role]

Key Deliverables

• [Deliverable 1]

Acceptance Criteria

• [Criterion 1]

---

Phase 2 (Future)

Goals

• [Long-term goal; details intentionally vague until earlier phases complete.]

---

Feature Traceability Matrix

Feature ID	Feature Name	Phase	Priority	Linked Epic(s)	Linked Stories	Status
[F-xxx]	[Name]	MVP	Must	[EPIC-x]	[Tracker IDs]	Draft

Risks and Blockers

Risk	Phase Impacted	Probability	Impact	Mitigation	Owner
[Risk]	[Phase]	[Low/Med/High]	[Low/Med/High]	[Mitigation]	[Role]

Source References

• Project Overview
• Project Requirements
• User Personas

---

Last Updated: YYYY-MM-DD