Planning Overview
Template Library
Planning Overview Template
Connect planning work to the accepted ES-102 requirements package before decomposing work into packages, owners, milestones, estimates, dependencies, and risks.
ES-103
Overview
Planning Context
Template purpose
Use this template to summarize the planning context before work is decomposed.
The planning overview should explain what the plan is intended to organize, what requirements and constraints drive the plan, what major work areas are expected, what assumptions shape the plan, and what concerns may affect architecture, implementation, verification, release, or operations.
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/planning_overview.md |
Source requirements evidence
docs/project-workspace/requirements/requirements_overview.md
docs/project-workspace/requirements/functional_requirements.md
docs/project-workspace/requirements/non_functional_requirements.md
docs/project-workspace/requirements/constraints.md
docs/project-workspace/requirements/use_cases.md
docs/project-workspace/requirements/traceability_matrix.md
docs/project-workspace/requirements/requirements_review.md
docs/project-workspace/requirements/requirements_readiness_summary.md
Planning objective
<Describe what this plan is intended to organize.>
Planning scope
| Area |
Included in This Plan? |
Notes |
| Requirements implementation |
<yes / no / partial> |
<notes> |
| Architecture preparation |
<yes / no / partial> |
<notes> |
| Evidence production |
<yes / no / partial> |
<notes> |
| AI-assisted work |
<yes / no / unknown / not applicable> |
<notes> |
| Verification work |
<yes / no / partial> |
<notes> |
| Governance or review work |
<yes / no / partial> |
<notes> |
| Operational preparation |
<yes / no / partial> |
<notes> |
Planning assumptions
| ID |
Assumption |
Impact if Wrong |
Validation / Follow-up |
| PA-001 |
<assumption> |
<impact> |
<validation or follow-up> |
Major work areas
| Work Area |
Description |
Source Evidence |
Expected Evidence Produced |
<area> |
<description> |
<source> |
<artifact, review, test, decision, log, evidence record> |
Evidence production strategy
| Evidence Family |
Planned Evidence |
Owner |
| Requirements |
<evidence> |
<owner> |
| Architecture |
<evidence> |
<owner> |
| Design |
<evidence> |
<owner> |
| Implementation |
<evidence> |
<owner> |
| Verification |
<evidence> |
<owner> |
| Governance |
<evidence> |
<owner> |
| Operations |
<evidence> |
<owner> |
AI-era planning considerations
| Question |
Planning Response |
| Will AI assistance be used in planning, design, implementation, testing, review, or documentation? |
<yes / no / unknown / limited> |
| What human review is required for AI-assisted work? |
<review expectation> |
| What AI-use evidence must be preserved? |
<AI use log, review record, prompt/output notes, evaluation evidence> |
| What work must not be delegated to AI? |
<prohibited or restricted work> |
Known planning concerns
| Concern ID |
Concern |
Impact |
Owner |
Follow-up |
| PC-001 |
<concern> |
<impact> |
<owner> |
<follow-up> |
Review checklist
- [ ] Source requirements evidence is identified.
- [ ] Planning objective is clear.
- [ ] Major work areas are identified.
- [ ] Evidence production is planned.
- [ ] AI-assisted work is addressed where relevant.
- [ ] Planning assumptions and concerns are visible.
- [ ] The plan is ready to be decomposed into work packages.