| 1 |
The plan states its start date, end date and the constraint it must fit |
Pass |
Unchanged from RC-003 and rechecked with MIL-006 included. |
| 2 |
Every milestone or gateway is listed once with its document, decision date and owner |
Pass |
Unchanged from RC-003 and rechecked with MIL-006 included. |
| 3 |
Every decision date lies inside the plan's window and is consistent with the dates in the linked MIL-* document |
Pass |
Decision dates equal the Target Date of MIL-001 to MIL-006 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 has a row for the purchase strategy improvement, mapped to MIL-006 and objective O1. |
| 5 |
Dependencies between gateways are stated, acyclic and consistent with the schedule order |
Pass |
Chain MIL-001 to MIL-006 is acyclic; MIL-006 follows MIL-005. |
| 6 |
The plan states what happens to later gateways and to the end date when a gateway is No-Go |
Pass |
Unchanged from RC-003 and rechecked with MIL-006 included. |
| 7 |
Owners, reviewers and escalation roles use Stakeholder Analysis IDs and match the governance RACI |
N-A |
No governance document is in scope of the Business Case; the only owner ID is S01, as in the MIL Ownership tables. |
| 8 |
Planning assumptions are listed with their source, and a changed baseline is recorded with its reason |
Pass |
Unchanged from RC-003 and rechecked with MIL-006 included. |
| 9 |
Plan risks are listed with impact and a mitigation, and trace to Business Case risks where they come from there |
Pass |
Plan Risks list a new risk (CPS does not rise) with a mitigation; two risks trace to Business Case risks. |
| 10 |
Open issues are listed, and none contradicts a statement elsewhere in the plan |
Pass |
Open Issues do not contradict the new row. |
| 11 |
Each gateway's main deliverable is stated and matches the deliverable of its MIL-* document |
Pass |
The main deliverable of MIL-006 in the plan matches its Deliverable section. |
| 12 |
Gateways that deliver user stories name them, and those that do not say why |
Pass |
Unchanged from RC-003 and rechecked with MIL-006 included. |
| 13 |
The schedule view (table, Gantt) and the dependency view agree with each other |
Pass |
Gantt bars, table and the chain agree. |
| 14 |
Each gateway is linked to its issue-tracker milestone, or marked as not yet synced |
Pass |
Milestone column blank until the sync. |
| 15 |
The plan is a singleton: one Project Plan per project, changes recorded in Version History |
Pass |
Unchanged from RC-003 and rechecked with MIL-006 included. |