Skip to content

Planning Workspace

ETIS Project Workspace

Planning Workspace

Work breakdown, milestones, roles, risks, dependencies, estimates.

ES-103 Project Repository Planning

Purpose

Turn requirements into an executable engineering plan. Planning should expose work, ownership, risk, dependencies, estimates, and readiness for architecture.

This directory should contain the project’s actual working artifacts for this lifecycle area. The links below intentionally point to the Template Library and, where available, the completed LMU/COICP example. Create the real project files in this directory when the project is ready to populate them.

What belongs here

Artifact Project File Name Template Completed Example
Planning Overview planning_overview.md Template Completed example
Work Breakdown Structure work_breakdown_structure.md Template Completed example
Milestones milestones.md Template Completed example
Roles And Responsibilities roles_and_responsibilities.md Template Completed example
Risk Register risk_register.md Template Completed example
Dependency Map dependency_map.md Template Completed example
Estimation Record estimation_record.md Template Completed example
Planning Review planning_review.md Template Completed example
Planning Readiness Summary planning_readiness_summary.md Template Completed example

Start from templates

Working pattern

  1. Open the relevant template.
  2. Create the same-named file in docs/project-workspace/planning/.
  3. Replace template guidance with project-specific evidence.
  4. Compare the result with the LMU/COICP example when available.
  5. Record open risks, assumptions, and unresolved questions.
  6. Finish with the review or readiness artifact for this stage.

Evidence quality bar

Quality What It Means
Specific Names actual project facts, stakeholders, systems, scenarios, risks, and decisions.
Traceable Connects back to earlier stages and forward to later stages.
Reviewable Gives another reviewer enough evidence to challenge or approve the work.
Current Reflects the project’s actual state rather than old intent.
Governable Makes AI use, exceptions, risks, release posture, and limitations visible.
Workspace Rule

Create project artifacts here. Learn the artifact structure from the Template Library. Learn the completed pattern from the LMU/COICP example.

Continue to Architecture

Move forward when this stage has enough project evidence and a clear readiness decision.

Open Architecture →