Consistent Deal & Ticket Creation Experience — Delivery Timeline
Delivery / Program Management — the living milestone & phase plan for this initiative.
statusis the doc lifecycle (linter enum), not the project's health.
Milestones
Effort is in man-days per discipline (BE/FE/QA…), mirroring the README's effort_* (canonical
there); Progress is man-days-done / total. Scaffolded — the DRI fills the man-days.
| Milestone | Effort (BE/FE/QA…) | Confidence | Progress | Target date | Owner | State |
|---|---|---|---|---|---|---|
| M1 — PRD approved | — | — | 0/0 | TBD | TBD | not-started |
| M2 — RFC agreed | — | — | 0/0 | TBD | TBD | not-started |
| M3 — Build complete | TBD | TBD | 0/0 | TBD | TBD | not-started |
| M4 — Shipped | — | — | 0/0 | TBD | TBD | not-started |
Phases
Phase 1 — Definition
- Land the PRD and its acceptance criteria; gate on
score-prdREADY. - Resolve open scope questions with the DRI before RFC work starts.
Phase 2 — Design & Build
- RFC agreed, then implementation against the story-table ACs.
- Test specs trace every composite
<STORY-ID>/AC-nid.
Notes
Dates to be confirmed once DRI is assigned and scope is finalized.