Plan the Day 21 repository: business case, stakeholders, plan and milestones
Adds the Business Case, Stakeholder Analysis, Domain Dictionary, Project Plan and milestones MIL-001 to MIL-003, with the review records RC-001 to RC-006 (all Go). The repository starts from the finished main of 020-snake-game, as S01 decided on 2026-10-08. The milestones and their 22 issues were synced to the git host.
This commit is contained in:
@@ -0,0 +1,70 @@
|
||||
# RC-001: Review of BC-001
|
||||
|
||||
## Metadata
|
||||
| Key | Value |
|
||||
| --- | --- |
|
||||
| ID | RC-001 |
|
||||
| CrossReference | [BC-001], [QC-BC-001], [QC-LANG-001], [DICT-001], [PP-001], [SA-001] |
|
||||
|
||||
## Version History
|
||||
| Date | Status | Author | Reviewer | Change | Commit |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| 2026-10-08 | Proposed | Jens Tirsvad Nielsen | S01 | Initial version | pending |
|
||||
|
||||
---
|
||||
|
||||
## Artifact Under Review
|
||||
|
||||
- Instance reviewed: [BC-001]
|
||||
- Checklist used: [QC-BC-001] and, for the language and domain, [QC-LANG-001]
|
||||
- Scope: full review
|
||||
- Language and domain: en / it
|
||||
- Language reviewer: none (S01 reads English and knows the IT domain)
|
||||
|
||||
## Checklist Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | ROI/Cost-Benefit analysis is quantitative, or where qualitative, is explicitly justified | Pass | Cost–Benefit Assessment is qualitative and says why: "this is an unpaid learning project with one participant, so money does not measure either side". |
|
||||
| 2 | Risks are identified with documented impact and mitigation | Pass | Risks table has 12 rows, each with an Impact and a Mitigation (checked by script: no empty cell); three are specific to this repository (assumed day-21 numbers, drift from the base, token leak). |
|
||||
| 3 | Success criteria are measurable, stating explicit targets rather than vague aspirations | Pass | 12 criteria, each with a Target and a Measure, e.g. criterion 7: `doxygen Doxyfile` ends with 0 warnings; criterion 8: 0 entries in `[project].dependencies`; criterion 9: 100% of the listed names exist. Criterion 4 is measured by a review of `src/`, which is checkable but not numeric. |
|
||||
| 4 | Scope explicitly separates In Scope vs Out of Scope | Pass | `### In Scope` and `### Out of Scope` subsections; Out of Scope names rebuilding the game and keeping the two repositories in step. |
|
||||
| 5 | Stakeholders are cross-referenced to Stakeholder Analysis IDs rather than re-described inline | Pass | Stakeholders table cites S01, S02 and S03 and states interests only; roles are not re-described. |
|
||||
| 6 | Methodology and quality-standard foundation are stated explicitly (e.g. ISO/IEC 25010, Larman) | Pass | Methodological and Standards Foundation names the framework, Larman, ISO/IEC 25010:2023, PEP 8/257/484, Doxygen and pytest. |
|
||||
| 7 | Assumptions and constraints are explicit and clearly distinguished from one another | Pass | Assumptions and Constraints are separate sections; the base being correct is an assumption, the plan window and the plan gate are constraints. |
|
||||
| 8 | Document supports executive decision-making with a clear, unambiguous recommendation | Pass | Recommendation: "Proceed — ...", one sentence. |
|
||||
|
||||
## Language and Domain Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | The Metadata table has a `Language` row and a `Domain` row, and neither is a placeholder | Pass | `Language` is `en` and `Domain` is `it` in the Metadata table. |
|
||||
| 2 | `Language` is a BCP 47 code and `Domain` is a value from the registry's domain list | Pass | `en` is a BCP 47 code; `it` is in the registry's domain list; `check-languages.sh --list` shows `en` and `it` for this document. |
|
||||
| 3 | The content (prose and table cells) is written in the stated language | Pass | All prose and table cells are English. Titles of lectures are quoted in English. |
|
||||
| 4 | The register matches the one the registry gives for the artifact type | Pass | Register is IT Executive English: short prose; code names and commands appear in backticks only where an objective or a measure needs them. |
|
||||
| 5 | Domain terms are the PO terms of the domain's dictionary, with no synonyms | Pass | Terms are those of [DICT-001] (screen, window, snake, segment, head, body, tail, move, direction, reversal, arrow key, food, refresh, eat, grow, score, scoreboard, wall, touch, game over, inheritance). Searched for the variants collision, collide, heading, boundary, border, apple, fruit, pellet, points, tile and step outside backticks. 'collisions' appears only in the quoted titles of the lectures; 'heading' (a section title) and 'collide' (for eat) were reworded and 'not at its edge' was changed before this review; 'edge of the screen' is the lecture's own phrase for the screen, not a second word for the wall; 'step' only means a project step, as the dictionary rules say. |
|
||||
| 6 | Metadata keys, section headings, IDs and statuses are in English | Pass | Keys, headings, IDs and statuses are English. |
|
||||
| 7 | No translated twin (`<name>.<language>.md`) exists beside the document | Pass | `docs/` holds one file per artifact; there is no `<name>.<language>.md`. |
|
||||
| 8 | A change of language or domain since the previous accepted version has a Version History row and was reviewed again | N-A | First version; there is no earlier accepted version. |
|
||||
| 9 | A reviewer competent in the domain, and in the language, has confirmed that the domain terms are used correctly | Pass | S01 (Product Owner and developer) reads English and knows the IT domain, and asked for this review in chat on 2026-10-08. The terms were also checked against [DICT-001] by the reviewing assistant; S01's own reading is an action item below. |
|
||||
| 10 | Abbreviations are spelled out on first use, in the stated language | Pass | Software Quality Assurance (SQA), Quality Criteria (QC), continuous integration (CI), Python Enhancement Proposals (PEP) and Python Package Index (PyPI) are spelled out on first use. ISO/IEC and UML appear only as the name of a standard and in the title of Larman's book. |
|
||||
|
||||
## Overall Verdict
|
||||
|
||||
Go — all Mandatory criteria pass. The checklist rows above were transcribed and assessed on 2026-10-08 by the assistant that drafted the documents, at S01's request in chat ("review them and start MIL-001"). S01 is named as reviewer and approves. This review is **not independent**: the drafter and the reviewer are the same assistant, and author and reviewer (S01) are one person in a single-person project (risk recorded in [BC-001] and [PP-001]). S01 has not yet read the document line by line and can overrule this verdict at the pull request.
|
||||
|
||||
## Action Items
|
||||
|
||||
| Action | Owner | Due |
|
||||
| --- | --- | --- |
|
||||
| Read BC-001 and confirm or overrule this `Go` before the pull request of MIL-001 is merged | S01 | 2026-10-09 |
|
||||
| Decide whether to create the governance document (`GOV`) and the traceability matrix (`TM`); no `TM` row could be added for this review because neither exists (open issue in [PP-001]) | S01 | 2026-10-09 |
|
||||
|
||||
---
|
||||
|
||||
[BC-001]: ../../business-case.md
|
||||
[QC-BC-001]: ../../../framework/qc/qc-business-case.md
|
||||
[QC-LANG-001]: ../../../framework/qc/qc-language-domain.md
|
||||
[DICT-001]: ../../dictionary.md
|
||||
[PP-001]: ../../project-plan.md
|
||||
[SA-001]: ../../stakeholder-analysis.md
|
||||
@@ -0,0 +1,70 @@
|
||||
# RC-002: Review of SA-001
|
||||
|
||||
## Metadata
|
||||
| Key | Value |
|
||||
| --- | --- |
|
||||
| ID | RC-002 |
|
||||
| CrossReference | [SA-001], [QC-SA-001], [QC-LANG-001], [BC-001], [DICT-001], [PP-001] |
|
||||
|
||||
## Version History
|
||||
| Date | Status | Author | Reviewer | Change | Commit |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| 2026-10-08 | Proposed | Jens Tirsvad Nielsen | S01 | Initial version | pending |
|
||||
|
||||
---
|
||||
|
||||
## Artifact Under Review
|
||||
|
||||
- Instance reviewed: [SA-001]
|
||||
- Checklist used: [QC-SA-001] and, for the language and domain, [QC-LANG-001]
|
||||
- Scope: full review
|
||||
- Language and domain: en / it
|
||||
- Language reviewer: none (S01 reads English and knows the IT domain)
|
||||
|
||||
## Checklist Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | Power/Interest grid is filled for every stakeholder, with no gaps or unclassified entries | Pass | S01, S02 and S03 each have a Power Level, an Interest Level and a Quadrant. |
|
||||
| 2 | Each stakeholder is assigned a unique, stable ID (e.g. S01-S11 style) reusable for RACI assignments in other artifacts | Pass | S01 to S03; the milestones and review records use them as owner and reviewer. |
|
||||
| 3 | Roles and organizational context are defined with explicit Power and Interest levels, not just narrative description | Pass | Role, Organization, Power and Interest are table columns. The levels of S02 and S03 were not stated by the Product Owner; the Purpose says they are proposals, and the Project Plan lists them as an open issue. |
|
||||
| 4 | Communication needs (channel, frequency, deliverable type) are mapped to project phases or milestones | Pass | Communication Requirements table maps S01, S02 and S03 to channel, frequency, deliverable and the milestones MIL-001 and MIL-003. |
|
||||
| 5 | Conflicting stakeholder interests are identified with documented mitigation or resolution strategies | Pass | Three conflicts, each with a mitigation (lecture style against structure; nothing to install against pytest and Doxygen; author equals reviewer). |
|
||||
| 6 | Stakeholder concerns are explicitly traced to Business Case objectives | Pass | Business Goal Alignment table; the objective numbers (1, 2 to 4, 5, 6, 7, 8, 9, 10) were checked against the ten objectives of BC-001 and match. |
|
||||
| 7 | Primary concerns are expressed in both business language and a recognized quality-attribute mapping (e.g. FURPS+) | Pass | The concern column of the summary table is in business language and the FURPS+ table maps eight concerns to an attribute. |
|
||||
| 8 | Document is understandable and navigable by non-technical stakeholders reviewing their own entry | Pass | Each stakeholder has one row and one rationale bullet in plain language; abbreviations are spelled out. |
|
||||
|
||||
## Language and Domain Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | The Metadata table has a `Language` row and a `Domain` row, and neither is a placeholder | Pass | `Language` is `en` and `Domain` is `it` in the Metadata table. |
|
||||
| 2 | `Language` is a BCP 47 code and `Domain` is a value from the registry's domain list | Pass | `en` is a BCP 47 code; `it` is in the registry's domain list; `check-languages.sh --list` shows `en` and `it` for this document. |
|
||||
| 3 | The content (prose and table cells) is written in the stated language | Pass | All prose and table cells are English. Titles of lectures are quoted in English. |
|
||||
| 4 | The register matches the one the registry gives for the artifact type | Pass | Register is IT Professional English: plain sentences, abbreviations spelled out, identifiers in backticks only in the concern table. |
|
||||
| 5 | Domain terms are the PO terms of the domain's dictionary, with no synonyms | Pass | Terms are those of [DICT-001] (game, snake, food, score, wall, tail, game over, arrow keys). The synonym search of the Business Case review was repeated on this document: only 'step' (project step) was found. |
|
||||
| 6 | Metadata keys, section headings, IDs and statuses are in English | Pass | Keys, headings, IDs and statuses are English. |
|
||||
| 7 | No translated twin (`<name>.<language>.md`) exists beside the document | Pass | `docs/` holds one file per artifact; there is no `<name>.<language>.md`. |
|
||||
| 8 | A change of language or domain since the previous accepted version has a Version History row and was reviewed again | N-A | First version; there is no earlier accepted version. |
|
||||
| 9 | A reviewer competent in the domain, and in the language, has confirmed that the domain terms are used correctly | Pass | S01 (Product Owner and developer) reads English and knows the IT domain, and asked for this review in chat on 2026-10-08. The terms were also checked against [DICT-001] by the reviewing assistant; S01's own reading is an action item below. |
|
||||
| 10 | Abbreviations are spelled out on first use, in the stated language | Pass | Quality Criteria (QC), RACI (Responsible, Accountable, Consulted, Informed) and FURPS+ are spelled out on first use. |
|
||||
|
||||
## Overall Verdict
|
||||
|
||||
Go — all Mandatory criteria pass. The checklist rows above were transcribed and assessed on 2026-10-08 by the assistant that drafted the documents, at S01's request in chat ("review them and start MIL-001"). S01 is named as reviewer and approves. This review is **not independent**: the drafter and the reviewer are the same assistant, and author and reviewer (S01) are one person in a single-person project (risk recorded in [BC-001] and [PP-001]). S01 has not yet read the document line by line and can overrule this verdict at the pull request.
|
||||
|
||||
## Action Items
|
||||
|
||||
| Action | Owner | Due |
|
||||
| --- | --- | --- |
|
||||
| Read SA-001 and confirm or overrule this `Go`; confirm the proposed Power and Interest levels of S02 and S03 | S01 | 2026-10-09 |
|
||||
| Decide whether to create the governance document (`GOV`) and the traceability matrix (`TM`); no `TM` row could be added for this review because neither exists (open issue in [PP-001]) | S01 | 2026-10-09 |
|
||||
|
||||
---
|
||||
|
||||
[SA-001]: ../../stakeholder-analysis.md
|
||||
[QC-SA-001]: ../../../framework/qc/qc-stakeholder-analysis.md
|
||||
[QC-LANG-001]: ../../../framework/qc/qc-language-domain.md
|
||||
[BC-001]: ../../business-case.md
|
||||
[DICT-001]: ../../dictionary.md
|
||||
[PP-001]: ../../project-plan.md
|
||||
@@ -0,0 +1,67 @@
|
||||
# RC-003: Review of DICT-001
|
||||
|
||||
## Metadata
|
||||
| Key | Value |
|
||||
| --- | --- |
|
||||
| ID | RC-003 |
|
||||
| CrossReference | [DICT-001], [QC-DICT-001], [QC-LANG-001], [BC-001], [PP-001] |
|
||||
|
||||
## Version History
|
||||
| Date | Status | Author | Reviewer | Change | Commit |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| 2026-10-08 | Proposed | Jens Tirsvad Nielsen | S01 | Initial version | pending |
|
||||
|
||||
---
|
||||
|
||||
## Artifact Under Review
|
||||
|
||||
- Instance reviewed: [DICT-001]
|
||||
- Checklist used: [QC-DICT-001] and, for the language and domain, [QC-LANG-001]
|
||||
- Scope: full review
|
||||
- Language and domain: en / it
|
||||
- Language reviewer: none (S01 reads English and knows the IT domain)
|
||||
|
||||
## Checklist Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | Every row has a PO term, its language, an IT term and a definition | Pass | 26 rows; a script found no empty cell. |
|
||||
| 2 | Each PO term maps to exactly one IT term and the reverse (no synonyms) | Pass | A script found no PO term and no IT term twice. `Turtle` (segment) and 'subclass of `Turtle`' (inheritance) are different IT terms. |
|
||||
| 3 | Every Domain Model concept has a row, and the Domain Model uses its PO term | N-A | No Domain Model exists in this project (the Dictionary's Rules section says so). |
|
||||
| 4 | The Operation Contracts, Sequence Diagrams, Design Class Diagrams and ERD use the IT term, not the PO term | N-A | None of these artifacts exists in this project. |
|
||||
| 5 | Definitions are written in the PO language and are one sentence | Pass | All definitions are English; a script found no definition with a second sentence. |
|
||||
| 6 | "Used as PO term in" and "Used as IT term in" name artifact types that exist in the project | Pass | The columns name BC, SA, PP and MIL (all exist) and PY, the source-code type of the catalog. |
|
||||
| 7 | The dictionary's `Language` and `Domain` rows, and the language of every row, match the PO language and domain in the project registry | Pass | Metadata `en` / `it` equals the registry's `PO language` and `PO domain`; the Language column of every row is `en`. |
|
||||
|
||||
## Language and Domain Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | The Metadata table has a `Language` row and a `Domain` row, and neither is a placeholder | Pass | `Language` is `en` and `Domain` is `it` in the Metadata table. |
|
||||
| 2 | `Language` is a BCP 47 code and `Domain` is a value from the registry's domain list | Pass | `en` is a BCP 47 code; `it` is in the registry's domain list; `check-languages.sh --list` shows `en` and `it` for this document. |
|
||||
| 3 | The content (prose and table cells) is written in the stated language | Pass | All prose and table cells are English. Titles of lectures are quoted in English. |
|
||||
| 4 | The register matches the one the registry gives for the artifact type | Pass | Register is IT Professional English: one-sentence definitions with the IT term in backticks. |
|
||||
| 5 | Domain terms are the PO terms of the domain's dictionary, with no synonyms | Pass | The document is the dictionary: its PO terms are its own rows. A script found no term twice. The two rules about 'step' and 'base' keep two project words out of the game vocabulary. |
|
||||
| 6 | Metadata keys, section headings, IDs and statuses are in English | Pass | Keys, headings, IDs and statuses are English. |
|
||||
| 7 | No translated twin (`<name>.<language>.md`) exists beside the document | Pass | `docs/` holds one file per artifact; there is no `<name>.<language>.md`. |
|
||||
| 8 | A change of language or domain since the previous accepted version has a Version History row and was reviewed again | N-A | First version; there is no earlier accepted version. |
|
||||
| 9 | A reviewer competent in the domain, and in the language, has confirmed that the domain terms are used correctly | Pass | S01 (Product Owner and developer) reads English and knows the IT domain, and asked for this review in chat on 2026-10-08. The terms were also checked against [DICT-001] by the reviewing assistant; S01's own reading is an action item below. |
|
||||
| 10 | Abbreviations are spelled out on first use, in the stated language | Pass | Product Owner (PO) and information technology (IT) are spelled out on first use; the artifact short names in the last two columns are the catalog's. |
|
||||
|
||||
## Overall Verdict
|
||||
|
||||
Go — all Mandatory criteria pass (criteria 3 and 4 are N-A because the Domain Model and the design artifacts do not exist in this project). The checklist rows above were transcribed and assessed on 2026-10-08 by the assistant that drafted the documents, at S01's request in chat ("review them and start MIL-001"). S01 is named as reviewer and approves. This review is **not independent**: the drafter and the reviewer are the same assistant, and author and reviewer (S01) are one person in a single-person project (risk recorded in [BC-001] and [PP-001]). S01 has not yet read the document line by line and can overrule this verdict at the pull request.
|
||||
|
||||
## Action Items
|
||||
|
||||
| Action | Owner | Due |
|
||||
| --- | --- | --- |
|
||||
| Read DICT-001 and confirm or overrule this `Go` | S01 | 2026-10-09 |
|
||||
|
||||
---
|
||||
|
||||
[DICT-001]: ../../dictionary.md
|
||||
[QC-DICT-001]: ../../../framework/qc/qc-dictionary.md
|
||||
[QC-LANG-001]: ../../../framework/qc/qc-language-domain.md
|
||||
[BC-001]: ../../business-case.md
|
||||
[PP-001]: ../../project-plan.md
|
||||
@@ -0,0 +1,70 @@
|
||||
# RC-004: Review of MIL-001
|
||||
|
||||
## Metadata
|
||||
| Key | Value |
|
||||
| --- | --- |
|
||||
| ID | RC-004 |
|
||||
| CrossReference | [MIL-001], [QC-MIL-001], [QC-LANG-001], [BC-001], [DICT-001], [PP-001] |
|
||||
|
||||
## Version History
|
||||
| Date | Status | Author | Reviewer | Change | Commit |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| 2026-10-08 | Proposed | Jens Tirsvad Nielsen | S01 | Initial version | pending |
|
||||
|
||||
---
|
||||
|
||||
## Artifact Under Review
|
||||
|
||||
- Instance reviewed: [MIL-001]
|
||||
- Checklist used: [QC-MIL-001] and, for the language and domain, [QC-LANG-001]
|
||||
- Scope: full review
|
||||
- Language and domain: en / it
|
||||
- Language reviewer: none (S01 reads English and knows the IT domain)
|
||||
|
||||
## Checklist Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable section lists the files of the foundation and the repository page; the proposed description and topics are written out. |
|
||||
| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Twelve Go/No-Go rows, each with a command or an observable result (for example `git check-ignore .venv .env __pycache__` lists all three). |
|
||||
| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies table: PP-001 accepted, and this milestone accepted with a Go review (plan-first gate). |
|
||||
| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability table maps to BC-001 objectives 6, 7, 8, 9 and 10 and Success Criteria 5 to 8, 10, 11 and 12; the numbers were checked against BC-001. |
|
||||
| 5 | Milestone owner and approving reviewer are identified | Pass | Ownership table: Owner S01, Approving reviewer S01 (same person; see verdict). |
|
||||
| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-10-09; BC-001 Constraints give a plan window ending 2026-10-16. |
|
||||
|
||||
## Language and Domain Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | The Metadata table has a `Language` row and a `Domain` row, and neither is a placeholder | Pass | `Language` is `en` and `Domain` is `it` in the Metadata table. |
|
||||
| 2 | `Language` is a BCP 47 code and `Domain` is a value from the registry's domain list | Pass | `en` is a BCP 47 code; `it` is in the registry's domain list; `check-languages.sh --list` shows `en` and `it` for this document. |
|
||||
| 3 | The content (prose and table cells) is written in the stated language | Pass | All prose and table cells are English. Titles of lectures are quoted in English. |
|
||||
| 4 | The register matches the one the registry gives for the artifact type | Pass | Register is IT Executive English: short prose; code names and commands appear in backticks only where a task or a check needs them. |
|
||||
| 5 | Domain terms are the PO terms of the domain's dictionary, with no synonyms | Pass | Terms are those of [DICT-001]. The synonym search found 'heading' (reworded to 'section title' before this review) and none else; the Go/No-Go table names commands because its criteria must be objectively checkable. |
|
||||
| 6 | Metadata keys, section headings, IDs and statuses are in English | Pass | Keys, headings, IDs and statuses are English. |
|
||||
| 7 | No translated twin (`<name>.<language>.md`) exists beside the document | Pass | `docs/` holds one file per artifact; there is no `<name>.<language>.md`. |
|
||||
| 8 | A change of language or domain since the previous accepted version has a Version History row and was reviewed again | N-A | First version; there is no earlier accepted version. |
|
||||
| 9 | A reviewer competent in the domain, and in the language, has confirmed that the domain terms are used correctly | Pass | S01 (Product Owner and developer) reads English and knows the IT domain, and asked for this review in chat on 2026-10-08. The terms were also checked against [DICT-001] by the reviewing assistant; S01's own reading is an action item below. |
|
||||
| 10 | Abbreviations are spelled out on first use, in the stated language | Pass | Continuous integration (CI) and application programming interface (API) are spelled out on first use; HTML and URL are not expanded. |
|
||||
|
||||
## Overall Verdict
|
||||
|
||||
Go — all Mandatory criteria pass. The checklist rows above were transcribed and assessed on 2026-10-08 by the assistant that drafted the documents, at S01's request in chat ("review them and start MIL-001"). S01 is named as reviewer and approves. This review is **not independent**: the drafter and the reviewer are the same assistant, and author and reviewer (S01) are one person in a single-person project (risk recorded in [BC-001] and [PP-001]). S01 has not yet read the document line by line and can overrule this verdict at the pull request.
|
||||
|
||||
## Action Items
|
||||
|
||||
| Action | Owner | Due |
|
||||
| --- | --- | --- |
|
||||
| Read MIL-001 and confirm or overrule this `Go` before the pull request of MIL-001 is merged | S01 | 2026-10-09 |
|
||||
| Confirm the proposed repository description and topics in the Deliverable section before task 7 sets them (done: S01 confirmed in chat and task 7 was carried out on 2026-10-08) | S01 | 2026-10-09 |
|
||||
| Confirm or overrule the code review RC-007 (`QC-PY-001`, verdict Go, written on 2026-10-08) before the pull request (Go/No-Go criterion 11) | S01 | 2026-10-09 |
|
||||
| Decide whether to create the governance document (`GOV`) and the traceability matrix (`TM`); no `TM` row could be added for this review because neither exists (open issue in [PP-001]) | S01 | 2026-10-09 |
|
||||
|
||||
---
|
||||
|
||||
[MIL-001]: ../../milestones/mil-001-project-foundation.md
|
||||
[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md
|
||||
[QC-LANG-001]: ../../../framework/qc/qc-language-domain.md
|
||||
[BC-001]: ../../business-case.md
|
||||
[DICT-001]: ../../dictionary.md
|
||||
[PP-001]: ../../project-plan.md
|
||||
@@ -0,0 +1,69 @@
|
||||
# RC-005: Review of MIL-002
|
||||
|
||||
## Metadata
|
||||
| Key | Value |
|
||||
| --- | --- |
|
||||
| ID | RC-005 |
|
||||
| CrossReference | [MIL-002], [QC-MIL-001], [QC-LANG-001], [BC-001], [DICT-001], [PP-001] |
|
||||
|
||||
## Version History
|
||||
| Date | Status | Author | Reviewer | Change | Commit |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| 2026-10-08 | Proposed | Jens Tirsvad Nielsen | S01 | Initial version | pending |
|
||||
|
||||
---
|
||||
|
||||
## Artifact Under Review
|
||||
|
||||
- Instance reviewed: [MIL-002]
|
||||
- Checklist used: [QC-MIL-001] and, for the language and domain, [QC-LANG-001]
|
||||
- Scope: full review
|
||||
- Language and domain: en / it
|
||||
- Language reviewer: none (S01 reads English and knows the IT domain)
|
||||
|
||||
## Checklist Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable section lists every source and test file of the game and the command that plays it. |
|
||||
| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Twelve Go/No-Go rows, each with a command or an observable result. The review found no criterion for the README, which would be out of date after the merge; criterion 11 and task 6 were added before this record. |
|
||||
| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies table: MIL-001 accepted and merged, which provides the package, the constants, the test set-up, the Doxyfile and the CI workflow. |
|
||||
| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability table maps to BC-001 objectives 1 to 5, 7, 8 and 9 and Success Criteria 1 to 5, 7, 9, 10 and 12, and records the deviation from `QC-PY-001` criterion 10 (no Design Class Diagram). |
|
||||
| 5 | Milestone owner and approving reviewer are identified | Pass | Ownership table: Owner S01, Approving reviewer S01 (same person; see verdict). |
|
||||
| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-10-12; BC-001 Constraints give a plan window ending 2026-10-16. |
|
||||
|
||||
## Language and Domain Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | The Metadata table has a `Language` row and a `Domain` row, and neither is a placeholder | Pass | `Language` is `en` and `Domain` is `it` in the Metadata table. |
|
||||
| 2 | `Language` is a BCP 47 code and `Domain` is a value from the registry's domain list | Pass | `en` is a BCP 47 code; `it` is in the registry's domain list; `check-languages.sh --list` shows `en` and `it` for this document. |
|
||||
| 3 | The content (prose and table cells) is written in the stated language | Pass | All prose and table cells are English. Titles of lectures are quoted in English. |
|
||||
| 4 | The register matches the one the registry gives for the artifact type | Pass | Register is IT Executive English: short prose; code names and commands appear in backticks only where a task or a check needs them. |
|
||||
| 5 | Domain terms are the PO terms of the domain's dictionary, with no synonyms | Pass | Terms are those of [DICT-001]. The synonym search found none outside backticks and quoted lecture titles. |
|
||||
| 6 | Metadata keys, section headings, IDs and statuses are in English | Pass | Keys, headings, IDs and statuses are English. |
|
||||
| 7 | No translated twin (`<name>.<language>.md`) exists beside the document | Pass | `docs/` holds one file per artifact; there is no `<name>.<language>.md`. |
|
||||
| 8 | A change of language or domain since the previous accepted version has a Version History row and was reviewed again | N-A | First version; there is no earlier accepted version. |
|
||||
| 9 | A reviewer competent in the domain, and in the language, has confirmed that the domain terms are used correctly | Pass | S01 (Product Owner and developer) reads English and knows the IT domain, and asked for this review in chat on 2026-10-08. The terms were also checked against [DICT-001] by the reviewing assistant; S01's own reading is an action item below. |
|
||||
| 10 | Abbreviations are spelled out on first use, in the stated language | Pass | Continuous integration (CI) is spelled out on first use (fixed before this review). |
|
||||
|
||||
## Overall Verdict
|
||||
|
||||
Go — all Mandatory criteria pass. The checklist rows above were transcribed and assessed on 2026-10-08 by the assistant that drafted the documents, at S01's request in chat ("review them and start MIL-001"). S01 is named as reviewer and approves. This review is **not independent**: the drafter and the reviewer are the same assistant, and author and reviewer (S01) are one person in a single-person project (risk recorded in [BC-001] and [PP-001]). S01 has not yet read the document line by line and can overrule this verdict at the pull request.
|
||||
|
||||
## Action Items
|
||||
|
||||
| Action | Owner | Due |
|
||||
| --- | --- | --- |
|
||||
| Read MIL-002 and confirm or overrule this `Go` before the pull request of MIL-002 is merged | S01 | 2026-10-12 |
|
||||
| Review the MIL-002 code against `QC-PY-001` and record the result as a separate `RC-*` before the pull request (Go/No-Go criterion 10) | S01 | 2026-10-12 |
|
||||
| Decide whether to create the governance document (`GOV`) and the traceability matrix (`TM`); no `TM` row could be added for this review because neither exists (open issue in [PP-001]) | S01 | 2026-10-12 |
|
||||
|
||||
---
|
||||
|
||||
[MIL-002]: ../../milestones/mil-002-adopt-the-game.md
|
||||
[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md
|
||||
[QC-LANG-001]: ../../../framework/qc/qc-language-domain.md
|
||||
[BC-001]: ../../business-case.md
|
||||
[DICT-001]: ../../dictionary.md
|
||||
[PP-001]: ../../project-plan.md
|
||||
@@ -0,0 +1,69 @@
|
||||
# RC-006: Review of MIL-003
|
||||
|
||||
## Metadata
|
||||
| Key | Value |
|
||||
| --- | --- |
|
||||
| ID | RC-006 |
|
||||
| CrossReference | [MIL-003], [QC-MIL-001], [QC-LANG-001], [BC-001], [DICT-001], [PP-001] |
|
||||
|
||||
## Version History
|
||||
| Date | Status | Author | Reviewer | Change | Commit |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| 2026-10-08 | Proposed | Jens Tirsvad Nielsen | S01 | Initial version | pending |
|
||||
|
||||
---
|
||||
|
||||
## Artifact Under Review
|
||||
|
||||
- Instance reviewed: [MIL-003]
|
||||
- Checklist used: [QC-MIL-001] and, for the language and domain, [QC-LANG-001]
|
||||
- Scope: full review
|
||||
- Language and domain: en / it
|
||||
- Language reviewer: none (S01 reads English and knows the IT domain)
|
||||
|
||||
## Checklist Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable section defines the comparison table and lists the ten lecture points that are its specification, each with the place in the code. |
|
||||
| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Fourteen Go/No-Go rows, each with a command or an observable result; the comparison with the video (criterion 13) is checkable because an undocumented difference is the No-Go. |
|
||||
| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies table: MIL-002 accepted and merged, because the game that is checked exists there. |
|
||||
| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability table maps to BC-001 objectives 1, 2, 3, 4, 7, 8, 9 and 10 and Success Criteria 1 to 7, 10 and 11, and records the deviation from `QC-PY-001` criterion 10. |
|
||||
| 5 | Milestone owner and approving reviewer are identified | Pass | Ownership table: Owner S01, Approving reviewer S01 (same person; see verdict). |
|
||||
| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-10-14; BC-001 Constraints give a plan window ending 2026-10-16, which leaves two buffer days. |
|
||||
|
||||
## Language and Domain Results
|
||||
|
||||
| # | Criterion | Status | Evidence/Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | The Metadata table has a `Language` row and a `Domain` row, and neither is a placeholder | Pass | `Language` is `en` and `Domain` is `it` in the Metadata table. |
|
||||
| 2 | `Language` is a BCP 47 code and `Domain` is a value from the registry's domain list | Pass | `en` is a BCP 47 code; `it` is in the registry's domain list; `check-languages.sh --list` shows `en` and `it` for this document. |
|
||||
| 3 | The content (prose and table cells) is written in the stated language | Pass | All prose and table cells are English. Titles of lectures are quoted in English. |
|
||||
| 4 | The register matches the one the registry gives for the artifact type | Pass | Register is IT Executive English: short prose; code names appear in backticks in the lecture-point table because each point must point at the code. |
|
||||
| 5 | Domain terms are the PO terms of the domain's dictionary, with no synonyms | Pass | Terms are those of [DICT-001]. 'collide' was changed to the dictionary term 'eats' before this review; 'collisions' remains only in the titles of the lectures, which are quoted. |
|
||||
| 6 | Metadata keys, section headings, IDs and statuses are in English | Pass | Keys, headings, IDs and statuses are English. |
|
||||
| 7 | No translated twin (`<name>.<language>.md`) exists beside the document | Pass | `docs/` holds one file per artifact; there is no `<name>.<language>.md`. |
|
||||
| 8 | A change of language or domain since the previous accepted version has a Version History row and was reviewed again | N-A | First version; there is no earlier accepted version. |
|
||||
| 9 | A reviewer competent in the domain, and in the language, has confirmed that the domain terms are used correctly | Pass | S01 (Product Owner and developer) reads English and knows the IT domain, and asked for this review in chat on 2026-10-08. The terms were also checked against [DICT-001] by the reviewing assistant; S01's own reading is an action item below. |
|
||||
| 10 | Abbreviations are spelled out on first use, in the stated language | Pass | No abbreviation is used that the Business Case does not spell out; the document uses none beyond S01 and the artifact IDs. |
|
||||
|
||||
## Overall Verdict
|
||||
|
||||
Go — all Mandatory criteria pass. The checklist rows above were transcribed and assessed on 2026-10-08 by the assistant that drafted the documents, at S01's request in chat ("review them and start MIL-001"). S01 is named as reviewer and approves. This review is **not independent**: the drafter and the reviewer are the same assistant, and author and reviewer (S01) are one person in a single-person project (risk recorded in [BC-001] and [PP-001]). S01 has not yet read the document line by line and can overrule this verdict at the pull request.
|
||||
|
||||
## Action Items
|
||||
|
||||
| Action | Owner | Due |
|
||||
| --- | --- | --- |
|
||||
| Read MIL-003 and confirm or overrule this `Go` before the pull request of MIL-003 is merged | S01 | 2026-10-14 |
|
||||
| Supply the lecture video (or its transcript) that the comparison in criterion 13 needs; the request holds only summaries | S01 | 2026-10-14 |
|
||||
| Decide whether to create the governance document (`GOV`) and the traceability matrix (`TM`); no `TM` row could be added for this review because neither exists (open issue in [PP-001]) | S01 | 2026-10-14 |
|
||||
|
||||
---
|
||||
|
||||
[MIL-003]: ../../milestones/mil-003-check-against-day-21.md
|
||||
[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md
|
||||
[QC-LANG-001]: ../../../framework/qc/qc-language-domain.md
|
||||
[BC-001]: ../../business-case.md
|
||||
[DICT-001]: ../../dictionary.md
|
||||
[PP-001]: ../../project-plan.md
|
||||
Reference in New Issue
Block a user