The MIL-003 milestone (id 74) and its issues #22 to #27 are created on Gitea. Creating them exposed a collision: task 6 of MIL-003 had the same title as task 6 of MIL-001, and sync-project.sh matches issues by title, so it overwrote the closed MIL-001 issue #6 (milestone and a Phase line). Issue #6 was restored, and MIL-003 task 6 is renamed "Review the visible-colours code against qc-programming-python", which is issue #27. No other task title is shared between the milestone documents. - MIL-003: rename task 6 (new Version History row, accepted by S01). - RC-008: add the delta confirmation for the rename; no criterion result changes (new row, accepted by S01). - PP-001: link the MIL-003 gateway to its Milestone (a link update, no new Version History row).
8.1 KiB
Project Plan: Hirst Painting
Metadata
| Key | Value |
|---|---|
| ID | PP-001 |
| CrossReference | BC-001, SA-001, MIL-001, MIL-002, MIL-003 |
| Language | en |
| Domain | it |
Version History
| Date | Status | Author | Reviewer | Change | Commit |
|---|---|---|---|---|---|
| 2026-10-08 | Deprecated | Jens Tirsvad Nielsen | S01 | Recorded the Go decisions of MIL-001 and MIL-002 Closed the reference-image open issue |
a6b17d3 |
| 2026-10-08 | Accepted | Jens Tirsvad Nielsen | S01 | Added gateway MIL-003 Visible Colours: schedule, timeline, scope coverage, dependency and a plan risk | 188b2e9 |
Purpose
This plan schedules the three phases of the Hirst painting project, the colour palette, the spot painting and the visible colours, inside the one-week limit that BC-001 sets (2026-10-07 to 2026-10-14). Each phase is a gateway with its own milestone document, and each gateway ends with a Go/No-Go decision by S01.
Planning Assumptions
- Week 1 starts 2026-10-07; the plan ends by 2026-10-14, per the Business Case assumption confirmed by S01.
- The baseline documents (BC-001, SA-001 and their review records) are finished on 2026-10-07, before the first phase starts.
- Phase length: two to five days, because the work is one small script. The palette phase is shorter because it is the smaller of the two.
- S01 owns every phase and takes every Go/No-Go decision; S01 is the only stakeholder in SA-001, so communication follows the review gates in that document.
- MIL-003 was added on 2026-10-08, after MIL-001 and MIL-002 had been decided Go, to meet objective O6 of BC-001; it runs from 2026-10-08 to 2026-10-10, inside the one-week limit.
- No user stories exist: the program has no user interaction beyond the exit click, so the Stories column is empty.
Gateway Schedule
| Gateway | Document | Window | Decision date | Owner | Stories | Main deliverable | Milestone |
|---|---|---|---|---|---|---|---|
| Colour palette | MIL-001 | 2026-10-07 to 2026-10-09 | 2026-10-09 | S01 | none | Palette function that returns the reference image's colours without white shades | MIL-001 milestone |
| Spot painting | MIL-002 | 2026-10-10 to 2026-10-14 | 2026-10-14 | S01 | none | Program that draws the 10 by 10 painting and meets SC1 to SC7 of BC-001 | MIL-002 milestone |
| Visible colours | MIL-003 | 2026-10-08 to 2026-10-10 | 2026-10-10 | S01 | none | Palette without faint colours: every colour has a contrast of 2.0 or more with white (O6, SC8 of BC-001) | MIL-003 milestone |
@startgantt
Project starts 2026-10-07
[Colour palette] starts 2026-10-07 and ends 2026-10-09
[Colour palette Go/No-Go] happens 2026-10-09
[Spot painting] starts 2026-10-10 and ends 2026-10-14
[Spot painting Go/No-Go] happens 2026-10-14
[Visible colours] starts 2026-10-08 and ends 2026-10-10
[Visible colours Go/No-Go] happens 2026-10-10
@endgantt
Scope Coverage
| Business Case scope item | Gateway |
|---|---|
One Python program using turtle, random and colorgram |
MIL-001 (colorgram part), MIL-002 (turtle and random part) |
| Palette extracted from one reference image, white shades removed | MIL-001 |
| Removal of faint colours from the palette: contrast with white below 2.0 | MIL-003 |
| Drawing the 10 by 10 dot grid: size, spacing, row change, heading | MIL-002 |
Screen handling: exitonclick, hidden turtle, pen up, drawing speed |
MIL-002 |
| Framework documents and review records for the plan-first workflow | Finished before each gateway (BC-001, SA-001, this plan, the milestone and their reviews); the review of each phase's code is a task in that phase |
Dependencies
Baseline documents → [MIL-001] Colour palette → [MIL-002] Spot painting → [MIL-003] Visible colours
MIL-002 needs the palette function from MIL-001. A No-Go on MIL-001 moves the start of MIL-002 by the days needed to rework and re-review; the one-week limit then has no slack, so S01 decides whether to extend it.
MIL-003 extends the palette function of MIL-001 and redraws the painting of MIL-002; both were decided Go on 2026-10-08, so nothing blocks it. A No-Go on MIL-003 leaves the accepted program as it is, so the earlier gateways stand.
Plan Risks
| Risk | Impact | Mitigation |
|---|---|---|
| The reference image is not supplied before the palette phase starts | MIL-001 cannot start its extraction task; the window of two to three days is lost | The tasks that do not need the image (toolchain check, white filter and its tests) come first; S01 decides on another image if this one stays unavailable |
| A No-Go on the palette phase | MIL-002 starts late and the one-week limit is missed | The palette phase is the smaller one and ends 2026-10-09, leaving five days for the painting phase |
| Review effort is large compared with the code | Time goes to documents instead of the program | Two phases, plain tasks, no use cases or design artifacts, as set out in BC-001 |
| The faint-colour filter changes code that MIL-001 and MIL-002 already delivered | An earlier test or criterion, such as SC3, could break | MIL-003 keeps the white-shade filter and its tests untouched and adds the contrast filter beside it; criterion 3 of MIL-003 requires every earlier test to pass |
| The Project Plan has no quality checklist | The plan is accepted on S01's judgement alone | S01 checks the plan against the one-week limit of BC-001 and the Go/No-Go criteria of both milestones |
Open Issues
- Reference image: resolved. S01 supplied
assets/20260524_132700.jpgon 2026-10-07, which completed task 4 of MIL-001. - Project Plan review: the Project Plan has no quality checklist yet, so it is
Acceptedwhen S01 says so in chat (done on 2026-10-07, and again on 2026-10-08 for the gateway decisions and for MIL-003); no review record is written for it. - Milestone links:
sync-project.sh --applyran on 2026-10-07 and created the two Milestones and issues #1 to #13 on the git host; the Milestone column links to them.
Gateway Decisions
The Go/No-Go decision of each gateway, taken by its owner (S01) in chat and recorded here by the assistant. The Decision date in the Gateway Schedule is the planned date; the date below is the actual one.
| Gateway | Document | Decision | Decided by | Decision date | Planned date | Basis |
|---|---|---|---|---|---|---|
| Colour palette | MIL-001 | Go | S01 | 2026-10-08 | 2026-10-09 | All five Go criteria met: imports and window, 30 colours, no white shade, 18 tests passing, code review RC-005 with verdict Go. Pull request PR 14 merged; Milestone closed on the git host |
| Spot painting | MIL-002 | Go | S01 | 2026-10-08 | 2026-10-14 | All six Go criteria met: 100 dots in 10 rows of 10, size 20 and 50 apart, colours from the palette, clean result with the window open until a click, drawn in 0.35 seconds, code review RC-006 with verdict Go. Pull request PR 16 merged; Milestone closed on the git host |
Both decisions came before the planned dates because every Go criterion was already met. The two open decisions on RC-006 (the display requirement of the tests and the pale palette colours) did not block either one.