Skip to content

Milestones

Template Library

Milestones Template

Define meaningful engineering checkpoints with readiness evidence, owners, target timing, and decision criteria.

ES-103 Milestones Checkpoints
Library AreaTemplate Library
Current PageMilestones
FocusPlanning checkpoints
UseDefine milestones and readiness evidence
Repository Areadocs/template-library/planning/
← Previous Roles and Responsibilities
Current Milestones
Next → Dependency Map

Template purpose

Use this template to define milestones for the project.

A milestone should not be a date label only. It should represent a meaningful engineering checkpoint where evidence is reviewed and a decision can be made.

Project

<Project name>

Document control

Field Value
Artifact owner <owner>
Primary reviewers <reviewers>
Status <draft / in review / accepted / revised>
Last updated <YYYY-MM-DD>
Related Engineering Stage ES-103 — Planning and Work Breakdown
Project workspace target docs/project-workspace/planning/milestones.md

Milestone register

ID Milestone Readiness Evidence Target Owner Decision Status
M-001 <milestone> <evidence required> <date or phase> <owner> <continue / revise / stop / defer> <open / planned / complete>

Milestone details

M-001 — <milestone>

Field Value
Purpose <purpose>
Target Date / Phase <date or phase>
Owner <owner>
Required Evidence <evidence required>
Review Participants <reviewers>
Decision Options <continue / revise / stop / defer>
Status <open / planned / complete>

Readiness criteria

  • <criterion>

Exit conditions

  • <condition>
<repository paths or future expected artifacts>

Stage-aligned milestones

Stage / Area Milestone Evidence Required
ES-104 Architecture <milestone> <architecture readiness evidence>
ES-105 Design <milestone> <design readiness evidence>
ES-106 Implementation Readiness <milestone> <implementation readiness evidence>
ES-109 Testing <milestone> <verification evidence>
ES-110 Release <milestone> <release readiness evidence>
ES-111–114 Operations and Stewardship <milestone> <operations and learning evidence>

Milestone risks

Milestone ID Risk Mitigation
<M-ID> <risk> <mitigation>

Review checklist

  • [ ] Milestones are tied to evidence, not just dates.
  • [ ] Each milestone has an owner.
  • [ ] Readiness criteria are defined.
  • [ ] Decision options are clear.
  • [ ] Milestone risks are identified.
  • [ ] Milestones support later architecture, design, implementation, verification, release, and operation.

Continue to Dependency Map

Identify dependencies that may block work, evidence production, architecture, or release.

Open Dependency Map →