Milestones

LMU/COICP Example

Milestones Example

Build the LMU/COICP planning baseline around concrete scenarios that flow into Architecture and later stages.

ES-103 Milestones Readiness Points

Example AreaLMU/COICP

Current PageMilestones

FocusLMU planning milestones

UseDefine readiness checkpoints

Repository Areadocs/examples/lmu-coicp/planning/

← Previous Work Breakdown Structure

Current Milestones

Next → Roles and Responsibilities

Example purpose

This artifact is part of the ES-103 — Planning package for the LMU Campus Operations and Incident Coordination Platform. It keeps planning tied to realistic LMU business problems rather than generic categories.

Project

LMU Campus Operations and Incident Coordination Platform

Document control

Field	Value
Artifact owner	COICP Product Engineer
Primary reviewers	COICP Product Owner, Architecture Review Board chair, IT security reviewer, AI reviewer, Compliance reviewer, Campus Safety liaison
Status	Accepted for ES-103 planning baseline
Last updated	2026-07-06
Related Engineering Stage	ES-103 — Planning
Project workspace target	docs/project-workspace/planning/milestones.md

Planning context

Field	Value
Source requirements package	ES-102 — Requirements and Constraints
Planning baseline produced	LMU-COICP-PLAN-001
Architecture baseline expected next	LMU-COICP-ARCH-001
Design baseline expected later	LMU-COICP-DES-001
Implementation baseline expected later	LMU-COICP-IMPL-001
Integrated baseline expected later	LMU-COICP-INT-001
Release candidate expected later	LMU-COICP-RC-001
Downstream release posture	Internal engineering review only
Planned downstream review environment	LMU-COICP Internal Engineering Review Environment
Planned downstream dataset	Spring Semester Synthetic Incident Dataset
Planned downstream synthetic records	421
Planned downstream reviewer accounts	24
Planned downstream review window	March 18–22, 2026
AI Incident Summary	Deferred / disabled
Operational pilot	Not approved

Milestone register

ID	Milestone	Readiness Evidence	Scenario Driver	Owner	Status
M-001	Scenario set locked	COICP-SYN-001, 118, 204, 219, 322, 407 selected and bounded	all	COICP Product Owner	Planned
M-002	Intake/handoff planning complete	COICP-SYN-001 and 118 workflow inputs documented	COICP-SYN-001 / 118	COICP Product Engineer	Planned
M-003	Evidence model inputs ready	creation, owner change, status change, handoff, closure, and scope-warning evidence identified	COICP-SYN-001 / 118 / 219 / 322	ARB chair	Planned
M-004	Role-scope planning complete	reviewer groups and allowed/denied actions drafted	COICP-SYN-204	IT security reviewer	Planned
M-005	AI disablement decision recorded	AI Incident Summary deferred/disabled through RC-001	all	AI reviewer / Product Owner	Planned
M-006	Emergency-boundary planning complete	COICP-SYN-322 block/redirect ownership assigned	COICP-SYN-322	Campus Safety liaison	Planned
M-007	Synthetic-data and retention boundary visible	Spring Semester Synthetic Incident Dataset and retention uncertainty recorded	all	Compliance reviewer	Planned
M-008	Internal-review assumptions documented	24 reviewer accounts, 421 records, March 18–22 review window	all	IT security reviewer / Product Owner	Planned
M-009	Architecture handoff ready	ES-104 inputs summarized and reviewed	all	ARB chair	Planned

Continue to Roles and Responsibilities

Move to the next planning artifact while preserving the same LMU scenario-driven flow.

Open Roles and Responsibilities →