Tirsvad-Udemy-100_days_of_code/014-higher_lower

Files

T

Tirsvad a1ff73580f Accept BC, SA, PP and MIL-001 after review

Review BC-001, SA-001, PP-001 and MIL-001 and record the results as
RC-001 to RC-004. All four verdicts are Go, so their Version History
rows become Accepted and the previous rows Deprecated. MIL-002 to
MIL-004 stay Proposed.

BC-001 failed criterion 1 (cost-benefit not justified as qualitative).
Add the justification and a target-completion constraint (2026-10-14)
that PP-001 and MIL-001 are checked against.

Add the Traceability Matrix (TM-001) and register RC and TM in the
artifact registry. PP has no QC checklist, so RC-003 checks the plan
against BC-001 and the milestones instead. Author and reviewer are
both S01, a deviation noted in each record.

Refs #5

2026-10-04 23:23:12 +08:00

4.4 KiB

Raw Blame History

Project Plan

Metadata

Key	Value
ID	PP-001
CrossReference	BC-001, SA-001, MIL-001, MIL-002, MIL-003, MIL-004, RC-003

Version History

Date	Status	Author	Reviewer	Change	Commit
2026-10-04	Deprecated	Jens Tirsvad Nielsen	S01	Initial version	ddfe96f
2026-10-04	Accepted	Jens Tirsvad Nielsen	S01	Accepted after review RC-003	pending

Purpose

Schedule the four phases that deliver the Higher Lower game (BC-001 objectives O1–O5) as a small, tested, documented Python project, with S01 reviewing each phase through its own branch and pull request.

Planning Assumptions

Week 1 starts 2026-10-04; the plan ends by 2026-10-14 (the Business Case sets no hard date; this is the author's evening-sized target, see Open Issues).
One phase per branch and pull request, each closing its issues.
Nothing under src/ or tests/ before the milestone is accepted and the task is a row in it.
Only S01 reviews (SA-001).

Gateway Schedule

Gateway	Document	Window	Decision date	Owner	Stories	Main deliverable
Project setup	MIL-001	2026-10-04 – 2026-10-06	2026-10-06	S01	—	pyproject, Doxyfile, skeleton, repo metadata
Game logic	MIL-002	2026-10-07 – 2026-10-09	2026-10-09	S01	—	Data, art, constants, pure functions, tests
Console game	MIL-003	2026-10-10 – 2026-10-12	2026-10-12	S01	—	Playable game loop with score, tests
Documentation and release	MIL-004	2026-10-13 – 2026-10-14	2026-10-14	S01	—	README, Doxygen run, review records

@startgantt
Project starts 2026-10-04
[Project setup] starts 2026-10-04 and ends 2026-10-06
[Project setup Go/No-Go] happens 2026-10-06
[Game logic] starts 2026-10-07 and ends 2026-10-09
[Game logic Go/No-Go] happens 2026-10-09
[Console game] starts 2026-10-10 and ends 2026-10-12
[Console game Go/No-Go] happens 2026-10-12
[Documentation and release] starts 2026-10-13 and ends 2026-10-14
[Documentation and release Go/No-Go] happens 2026-10-14
@endgantt

Scope Coverage

Business Case scope item	Gateway
`src/`, `tests/`, `docs/` layout, `pyproject.toml`, `.gitignore`, `Doxyfile`	MIL-001
Repository description and topics	MIL-001
Assignment data set, `logo` and `vs` art	MIL-002
Random pair selection, answer checking	MIL-002
Console game, score tracking	MIL-003
`README.md`, venv and test instructions	MIL-004

Dependencies

MIL-001 → MIL-002 → MIL-003 → MIL-004

A No-Go on any phase moves all later windows by the rework time.

Plan Risks

Risk	Impact	Mitigation
README template not supplied	README task blocked	Ask S01 before MIL-004 starts
Host token missing or lacking scope	Cannot sync issues or set topics	Token read from `.env` for personal use only; ask S01 if absent
Doxygen not installed locally	Cannot verify docs build	Treat as a No-Go note; install or review comments manually

Open Issues

README template: the brief says "using the template below" but none was included. Needed before MIL-004.
Python version: "greater than 3.13" is planned as >=3.13; confirm if strictly 3.14+ is meant.
Target dates are proposed, not stated in the brief; confirm.
The brief links the organisation; the origin remote is the repository 014-higher_lower within it, which is what will be synced.

4.4 KiB Raw Blame History Unescape Escape