| 1 |
The plan states its start date, end date and the constraint it must fit |
Pass |
Planning Assumptions state start 2026-10-28 and end 2026-11-04 per the one-week Business Case constraint. |
| 2 |
Every milestone or gateway is listed once with its document, decision date and owner |
Pass |
Five gateway rows, each linking its MIL document, decision date and owner S01. |
| 3 |
Every decision date lies inside the plan's window and is consistent with the dates in the linked MIL-* document |
Pass |
Decision dates 2026-10-29, 10-30, 10-31, 11-02, 11-04 equal the Target Date of MIL-001 to MIL-005 and lie inside the window. |
| 4 |
Every in-scope item of the Business Case is delivered at a named gateway (scope coverage) |
Pass |
Scope Coverage table maps every In Scope item to a gateway. |
| 5 |
Dependencies between gateways are stated, acyclic and consistent with the schedule order |
Pass |
Chain MIL-001 to MIL-005 is acyclic and matches the schedule order. |
| 6 |
The plan states what happens to later gateways and to the end date when a gateway is No-Go |
Pass |
Dependencies section says a No-Go returns the phase to its owner, later gateways move, and S01 alone decides an end-date move. |
| 7 |
Owners, reviewers and escalation roles use Stakeholder Analysis IDs and match the governance RACI |
N-A |
No governance document is in scope of [BC-001]; all owners use the SA ID S01, matching the MIL Ownership tables. |
| 8 |
Planning assumptions are listed with their source, and a changed baseline is recorded with its reason |
Pass |
Planning Assumptions list start, length, reviewer stand-in and cadence with sources. |
| 9 |
Plan risks are listed with impact and a mitigation, and trace to Business Case risks where they come from there |
Pass |
Plan Risks have impact and mitigation; two trace to Business Case risks. |
| 10 |
Open issues are listed, and none contradicts a statement elsewhere in the plan |
Pass |
Open Issues name the repository-name difference and the earlier solution; neither contradicts the plan. |
| 11 |
Each gateway's main deliverable is stated and matches the deliverable of its MIL-* document |
Pass |
Main deliverable column matches each MIL Deliverable. |
| 12 |
Gateways that deliver user stories name them, and those that do not say why |
Pass |
Stories column says 'none (technical tasks)'. |
| 13 |
The schedule view (table, Gantt) and the dependency view agree with each other |
Pass |
Gantt bars and the table use the same dates; the chain matches the dependency list. |
| 14 |
Each gateway is linked to its issue-tracker milestone, or marked as not yet synced |
Pass |
Milestone column is blank because no sync has happened yet. |
| 15 |
The plan is a singleton: one Project Plan per project, changes recorded in Version History |
Pass |
Single plan file docs/project-plan.md with one Version History row. |