Planning baseline for the Higher Lower game (Udemy 100 Days of Code, day 14). No code under src/ or tests/.
Business Case (BC-001), Stakeholder Analysis (SA-001), Project Plan (PP-001)
Four milestones with Go/No-Go criteria and task tables: MIL-001 Project setup, MIL-002 Game logic, MIL-003 Console game, MIL-004 Documentation and release
Milestones 36-39 and issues #1-#20 synced to the host; the Project Plan links the milestones
Repository description and topics set via the API
BC-001, SA-001, PP-001 and MIL-001 reviewed (RC-001 to RC-004, all Go) and Accepted; MIL-002 to MIL-004 stay Proposed
## Summary
Planning baseline for the Higher Lower game (Udemy 100 Days of Code, day 14). No code under `src/` or `tests/`.
- Business Case (BC-001), Stakeholder Analysis (SA-001), Project Plan (PP-001)
- Four milestones with Go/No-Go criteria and task tables: MIL-001 Project setup, MIL-002 Game logic, MIL-003 Console game, MIL-004 Documentation and release
- Milestones 36-39 and issues #1-#20 synced to the host; the Project Plan links the milestones
- Repository description and topics set via the API
- BC-001, SA-001, PP-001 and MIL-001 reviewed (RC-001 to RC-004, all Go) and Accepted; MIL-002 to MIL-004 stay Proposed
- Traceability Matrix (TM-001) added
## Open items
- README template not supplied yet (blocks #17)
- `requires-python` planned as `>=3.13`; confirm if 3.14+ is meant
- Target dates (2026-10-06 to 2026-10-14) are proposed
- UC-001 "Play a game" is referenced by #13 and not yet created
- Author and reviewer are both S01 (single participant); noted in each review record
Closes #5
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Planning baseline for the Higher Lower game (Udemy 100 Days of Code, day 14). No code under
src/ortests/.Open items
requires-pythonplanned as>=3.13; confirm if 3.14+ is meantCloses #5