Planning Templates

Template Library

Planning Templates

Use the ES-103 template family to convert accepted requirements into responsible work packages, ownership, estimates, dependencies, risks, milestones, and readiness for architecture.

ES-103 Planning Package Start Here

Library AreaTemplate Library

Current PagePlanning Templates

FocusPlanning package

UseSelect and complete ES-103 artifacts

Repository Areadocs/template-library/planning/

← Previous Requirements Readiness Summary

Current Planning Templates

Next → Planning Overview

Purpose

These templates support ES-103 — Planning and Work Breakdown.

Use this family to organize engineering work after requirements are accepted. ES-103 turns requirements and constraints into deliverable-oriented work packages, evidence responsibilities, risk ownership, dependencies, milestones, estimates, and readiness for architecture work.

Recommended workflow

Requirements Readiness Summary
      ↓
Planning Overview
      ↓
Work Breakdown Structure
      ↓
Roles and Responsibilities
      ↓
Milestones
      ↓
Dependency Map
      ↓
Estimation Record
      ↓
Risk Register
      ↓
Planning Review
      ↓
Planning Readiness Summary
      ↓
ES-104 Architecture and Technical Approach

Copy location

Do not edit the reusable templates directly. Copy completed project versions into:

docs/project-workspace/planning/

Template set

01

Planning Overview

Summarize planning objective, source requirements, work areas, assumptions, and concerns.

02

Work Breakdown Structure

Define deliverable-oriented work packages with owners, dependencies, estimates, and evidence.

03

Roles and Responsibilities

Assign accountability for work, reviews, AI verification, evidence, and decisions.

04

Milestones

Define planning milestones and readiness criteria.

05

Dependency Map

Identify internal, external, architecture, data, AI, governance, and operational dependencies.

06

Estimation Record

Capture estimates, confidence, uncertainty, basis, and investigation needs.

07

Risk Register

Track scope, schedule, technical, data, AI, security, governance, and operational risks.

08

Planning Review

Review plan quality, ownership, dependencies, evidence production, risks, and readiness.

09

Planning Readiness Summary

Summarize readiness to begin ES-104 architecture and technical approach.

Completion expectations

Question	Evidence
What requirements and constraints drive the plan?	planning_overview.md
What work must be done?	work_breakdown_structure.md
Who owns work and evidence?	roles_and_responsibilities.md
What are the major checkpoints?	milestones.md
What dependencies can block progress?	dependency_map.md
How much effort is expected and how confident are we?	estimation_record.md
What risks must be managed?	risk_register.md
Has the plan been reviewed?	planning_review.md
Is architecture work ready to begin?	planning_readiness_summary.md

Common Pitfall

Do not turn planning into a task dump. ES-103 should produce accountable, evidence-centered work packages that trace to requirements and prepare architecture work.

Engineering Insight

A good plan makes invisible engineering obligations visible: ownership, evidence, dependencies, risk, uncertainty, and readiness.

Begin with Planning Overview

Start by connecting ES-103 planning work to the accepted ES-102 requirements package.

Open Planning Overview →