diff --git a/docs/sqa/reviews/rc-001-business-case.md b/docs/sqa/reviews/rc-001-business-case.md index 1b9972d..ad2c538 100644 --- a/docs/sqa/reviews/rc-001-business-case.md +++ b/docs/sqa/reviews/rc-001-business-case.md @@ -1,48 +1,49 @@ -# Review Record: BC-001 Business Case - -## Metadata -| Key | Value | -| --- | --- | -| ID | RC-001 | -| CrossReference | [BC-001], [QC-BC-001] | - -## Version History -| Date | Status | Author | Reviewer | Change | Commit | -| --- | --- | --- | --- | --- | --- | -| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | [c017c06] | - ---- - -## Artifact Under Review - -- Instance reviewed: [BC-001] -- Checklist used: [QC-BC-001] (`QC-BC-001`) - -## Checklist Results - -| # | Criterion | Status | Evidence/Notes | -| --- | --- | --- | --- | -| 1 | ROI/Cost-Benefit analysis is quantitative, or where qualitative, is explicitly justified | Pass | The Cost–Benefit Assessment states costs as qualitative with no external cost and lists benefits; the qualitative form is labelled. | -| 2 | Risks are identified with documented impact and mitigation | Pass | Risks table has Risk, Impact and Mitigation for every row. | -| 3 | Success criteria are measurable, stating explicit targets rather than vague aspirations | Pass | Four criteria, each with a target and a measure. | -| 4 | Scope explicitly separates In Scope vs Out of Scope | Pass | Scope has separate In Scope and Out of Scope lists. | -| 5 | Stakeholders are cross-referenced to Stakeholder Analysis IDs rather than re-described inline | Pass | Stakeholders table uses S01 to S05; the ID, not a role description, identifies each. | -| 6 | Methodology and quality-standard foundation are stated explicitly (e.g. ISO/IEC 25010, Larman) | Pass | Methodological and Standards Foundation cites the framework, Larman and ISO/IEC 25010:2023. | -| 7 | Assumptions and constraints are explicit and clearly distinguished from one another | Pass | Separate Assumptions and Constraints sections. The 2026-10-10 change edits the mirror assumption only. | -| 8 | Document supports executive decision-making with a clear, unambiguous recommendation | Pass | Recommendation section: Proceed, with the reason. | - -## Overall Verdict - -Go — all eight criteria pass. S01 gave the Go in chat on 2026-10-10 for the revision that changes the mirror assumption to at most one GitHub push mirror. The author and the approving reviewer are the same person (S01); an independent review by S05 is recorded as an action item. - -## Action Items - -| Action | Owner | Due | -| --- | --- | --- | -| Independent review of this record and of BC-001 by a person other than the author (the rule that the reviewer must not be the author) | S05 | 2026-10-17 | - ---- - -[BC-001]: ../../business-case.md -[QC-BC-001]: ../../../framework/qc/qc-business-case.md -[c017c06]: https://git.tirsystem.com/TirSystem/github-action/commit/c017c06789424305b31f19e48238ad14231e8113 +# Review Record: BC-001 Business Case + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-001 | +| CrossReference | [BC-001], [QC-BC-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Deprecated | Jens Tirsvad Nielsen | S05 | Initial version | [c017c06] | +| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S05 | S05 review approved (reported by S01)
Independence action item closed | pending | + +--- + +## Artifact Under Review + +- Instance reviewed: [BC-001] +- Checklist used: [QC-BC-001] (`QC-BC-001`) + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | ROI/Cost-Benefit analysis is quantitative, or where qualitative, is explicitly justified | Pass | The Cost–Benefit Assessment states costs as qualitative with no external cost and lists benefits; the qualitative form is labelled. | +| 2 | Risks are identified with documented impact and mitigation | Pass | Risks table has Risk, Impact and Mitigation for every row. | +| 3 | Success criteria are measurable, stating explicit targets rather than vague aspirations | Pass | Four criteria, each with a target and a measure. | +| 4 | Scope explicitly separates In Scope vs Out of Scope | Pass | Scope has separate In Scope and Out of Scope lists. | +| 5 | Stakeholders are cross-referenced to Stakeholder Analysis IDs rather than re-described inline | Pass | Stakeholders table uses S01 to S05; the ID, not a role description, identifies each. | +| 6 | Methodology and quality-standard foundation are stated explicitly (e.g. ISO/IEC 25010, Larman) | Pass | Methodological and Standards Foundation cites the framework, Larman and ISO/IEC 25010:2023. | +| 7 | Assumptions and constraints are explicit and clearly distinguished from one another | Pass | Separate Assumptions and Constraints sections. The 2026-10-10 change edits the mirror assumption only. | +| 8 | Document supports executive decision-making with a clear, unambiguous recommendation | Pass | Recommendation section: Proceed, with the reason. | + +## Overall Verdict + +Go — all eight criteria pass. S01 gave the Go in chat on 2026-10-10 for the revision that changes the mirror assumption to at most one GitHub push mirror. The author and the approving reviewer are the same person (S01); S05 completed the independent review on 2026-10-10 (reported by S01). + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Independent review of this record and of BC-001 by a person other than the author (the rule that the reviewer must not be the author) | S05 | Done 2026-10-10 | + +--- + +[BC-001]: ../../business-case.md +[QC-BC-001]: ../../../framework/qc/qc-business-case.md +[c017c06]: https://git.tirsystem.com/TirSystem/github-action/commit/c017c06789424305b31f19e48238ad14231e8113 diff --git a/docs/sqa/reviews/rc-002-project-plan.md b/docs/sqa/reviews/rc-002-project-plan.md index 0c50ffe..a776ca0 100644 --- a/docs/sqa/reviews/rc-002-project-plan.md +++ b/docs/sqa/reviews/rc-002-project-plan.md @@ -1,48 +1,48 @@ -# Review Record: PP-001 Project Plan - -## Metadata -| Key | Value | -| --- | --- | -| ID | RC-002 | -| CrossReference | [PP-001], [BC-001] | - -## Version History -| Date | Status | Author | Reviewer | Change | Commit | -| --- | --- | --- | --- | --- | --- | -| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | [c017c06] | - ---- - -## Artifact Under Review - -- Instance reviewed: [PP-001] -- Checklist used: none: the Project Plan has no QC checklist (catalog and `PP.md` reference). Validated against the Business Case [BC-001] constraints and the Go / No-Go criteria of each listed milestone, as `PP.md` prescribes. - -## Checklist Results - -| # | Criterion | Status | Evidence/Notes | -| --- | --- | --- | --- | -| 1 | Every milestone in the plan has a `MIL-*` document and the plan's dates equal that document's target date | Pass | MIL-001 to MIL-004 exist; decision dates 2026-10-17, 10-31, 11-14, 11-28 match the Target Date of each milestone. | -| 2 | Every Business Case scope item is covered by a gateway | Pass | Scope Coverage maps validation, documentation, quality checks and release to MIL-001 to MIL-004. | -| 3 | The schedule respects the Business Case constraints | Pass | The Business Case sets no deadline; the plan states its dates are proposals. The constraint that nothing is written before a milestone is accepted is repeated in Planning Assumptions. | -| 4 | Dependencies between milestones are stated | Pass | Dependencies section gives MIL-001 to MIL-002 to MIL-003 to MIL-004. | -| 5 | Every gateway has an owner who is a stakeholder ID | Pass | All four gateways are owned by S05. | -| 6 | Plan content is consistent with the revised mirror behaviour | Pass | UC candidate 1 now describes no GitHub mirror as a successful skip and several mirrors as a failure. | -| 7 | Open Issues are current | Fail | Open Issues still lists the decisions for MIL-001 task 1 and task 3 as open; both were decided and recorded in MIL-001. | - -## Overall Verdict - -Go — S01 gave the Go in chat on 2026-10-10 for the revision to UC candidate 1. One stale entry in Open Issues does not affect the schedule or the changed use case; it is recorded as an action item. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. - -## Action Items - -| Action | Owner | Due | -| --- | --- | --- | -| Remove the answered MIL-001 task 1 and task 3 items from Open Issues in PP-001, with a Version History row | S01 | 2026-10-17 | -| Confirm the proposed dates and the start week (already listed in Open Issues) | S01 | 2026-10-17 | - ---- - -[PP-001]: ../../project-plan.md -[BC-001]: ../../business-case.md -[c017c06]: https://git.tirsystem.com/TirSystem/github-action/commit/c017c06789424305b31f19e48238ad14231e8113 +# Review Record: PP-001 Project Plan + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-002 | +| CrossReference | [PP-001], [BC-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S05 | Initial version | [c017c06] | + +--- + +## Artifact Under Review + +- Instance reviewed: [PP-001] +- Checklist used: none: the Project Plan has no QC checklist (catalog and `PP.md` reference). Validated against the Business Case [BC-001] constraints and the Go / No-Go criteria of each listed milestone, as `PP.md` prescribes. + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | Every milestone in the plan has a `MIL-*` document and the plan's dates equal that document's target date | Pass | MIL-001 to MIL-004 exist; decision dates 2026-10-17, 10-31, 11-14, 11-28 match the Target Date of each milestone. | +| 2 | Every Business Case scope item is covered by a gateway | Pass | Scope Coverage maps validation, documentation, quality checks and release to MIL-001 to MIL-004. | +| 3 | The schedule respects the Business Case constraints | Pass | The Business Case sets no deadline; the plan states its dates are proposals. The constraint that nothing is written before a milestone is accepted is repeated in Planning Assumptions. | +| 4 | Dependencies between milestones are stated | Pass | Dependencies section gives MIL-001 to MIL-002 to MIL-003 to MIL-004. | +| 5 | Every gateway has an owner who is a stakeholder ID | Pass | All four gateways are owned by S05. | +| 6 | Plan content is consistent with the revised mirror behaviour | Pass | UC candidate 1 now describes no GitHub mirror as a successful skip and several mirrors as a failure. | +| 7 | Open Issues are current | Fail | Open Issues still lists the decisions for MIL-001 task 1 and task 3 as open; both were decided and recorded in MIL-001. | + +## Overall Verdict + +Go — S01 gave the Go in chat on 2026-10-10 for the revision to UC candidate 1. One stale entry in Open Issues does not affect the schedule or the changed use case; it is recorded as an action item. The author and the approving reviewer are the same person (S01); the independent S05 review is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Remove the answered MIL-001 task 1 and task 3 items from Open Issues in PP-001, with a Version History row | S01 | 2026-10-17 | +| Confirm the proposed dates and the start week (already listed in Open Issues) | S01 | 2026-10-17 | + +--- + +[PP-001]: ../../project-plan.md +[BC-001]: ../../business-case.md +[c017c06]: https://git.tirsystem.com/TirSystem/github-action/commit/c017c06789424305b31f19e48238ad14231e8113 diff --git a/docs/sqa/reviews/rc-003-mil-001.md b/docs/sqa/reviews/rc-003-mil-001.md index 1c3bf36..cb1011f 100644 --- a/docs/sqa/reviews/rc-003-mil-001.md +++ b/docs/sqa/reviews/rc-003-mil-001.md @@ -1,46 +1,46 @@ -# Review Record: MIL-001 Stabilise the metadata sync - -## Metadata -| Key | Value | -| --- | --- | -| ID | RC-003 | -| CrossReference | [MIL-001], [QC-MIL-001] | - -## Version History -| Date | Status | Author | Reviewer | Change | Commit | -| --- | --- | --- | --- | --- | --- | -| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | [c017c06] | - ---- - -## Artifact Under Review - -- Instance reviewed: [MIL-001] -- Checklist used: [QC-MIL-001] (`QC-MIL-001`) - -## Checklist Results - -| # | Criterion | Status | Evidence/Notes | -| --- | --- | --- | --- | -| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable section: one canonical workflow, passing validation and tests, an accurate README and a manual run. | -| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Five criteria, each with an objectively checkable Go and No-Go column. | -| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: none, first milestone. | -| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-001 to O1 and O2 of BC-001. | -| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | -| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-10-17, marked proposed; the Business Case sets no deadline, so there is nothing to contradict. | - -## Overall Verdict - -Go — all six criteria pass. S01 gave the Go in chat on 2026-10-10 for the amendment of the task 1 decision (zero GitHub mirrors is a successful skip) and the matching task 5 test scope. Go / No-Go criterion 5 (manual run on Gitea) is still open as task 7 (issue 7) and is not changed by this amendment. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. - -## Action Items - -| Action | Owner | Due | -| --- | --- | --- | -| Run the manual `workflow_dispatch` check on Gitea for the amended behaviour: a repository with a GitHub mirror and one without (task 7) | S05 | 2026-10-17 | - ---- - -[MIL-001]: ../../milestones/mil-001-stabilise-metadata-sync.md -[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md -[c017c06]: https://git.tirsystem.com/TirSystem/github-action/commit/c017c06789424305b31f19e48238ad14231e8113 +# Review Record: MIL-001 Stabilise the metadata sync + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-003 | +| CrossReference | [MIL-001], [QC-MIL-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S05 | Initial version | [c017c06] | + +--- + +## Artifact Under Review + +- Instance reviewed: [MIL-001] +- Checklist used: [QC-MIL-001] (`QC-MIL-001`) + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable section: one canonical workflow, passing validation and tests, an accurate README and a manual run. | +| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Five criteria, each with an objectively checkable Go and No-Go column. | +| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: none, first milestone. | +| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-001 to O1 and O2 of BC-001. | +| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | +| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-10-17, marked proposed; the Business Case sets no deadline, so there is nothing to contradict. | + +## Overall Verdict + +Go — all six criteria pass. S01 gave the Go in chat on 2026-10-10 for the amendment of the task 1 decision (zero GitHub mirrors is a successful skip) and the matching task 5 test scope. Go / No-Go criterion 5 (manual run on Gitea) is still open as task 7 (issue 7) and is not changed by this amendment. The author and the approving reviewer are the same person (S01); the independent S05 review is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Run the manual `workflow_dispatch` check on Gitea for the amended behaviour: a repository with a GitHub mirror and one without (task 7) | S05 | 2026-10-17 | + +--- + +[MIL-001]: ../../milestones/mil-001-stabilise-metadata-sync.md +[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md +[c017c06]: https://git.tirsystem.com/TirSystem/github-action/commit/c017c06789424305b31f19e48238ad14231e8113 diff --git a/docs/sqa/reviews/rc-004-stakeholder-analysis.md b/docs/sqa/reviews/rc-004-stakeholder-analysis.md index b4495b0..92e8bee 100644 --- a/docs/sqa/reviews/rc-004-stakeholder-analysis.md +++ b/docs/sqa/reviews/rc-004-stakeholder-analysis.md @@ -1,49 +1,49 @@ -# Review Record: SA-001 Stakeholder Analysis - -## Metadata -| Key | Value | -| --- | --- | -| ID | RC-004 | -| CrossReference | [SA-001], [QC-SA-001] | - -## Version History -| Date | Status | Author | Reviewer | Change | Commit | -| --- | --- | --- | --- | --- | --- | -| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | - ---- - -## Artifact Under Review - -- Instance reviewed: [SA-001] -- Checklist used: [QC-SA-001] - -## Checklist Results - -| # | Criterion | Status | Evidence/Notes | -| --- | --- | --- | --- | -| 1 | Power/Interest grid is filled for every stakeholder, with no gaps or unclassified entries | Pass | S01 to S05 each have Power, Interest and Quadrant. | -| 2 | Each stakeholder is assigned a unique, stable ID reusable for RACI assignments in other artifacts | Pass | IDs S01 to S05 are used by BC-001, PP-001 and the milestones. | -| 3 | Roles and organizational context are defined with explicit Power and Interest levels, not just narrative description | Pass | Role, organization and HIGH/MEDIUM/LOW levels per stakeholder, with a rationale section. | -| 4 | Communication needs (channel, frequency, deliverable type) are mapped to project phases or milestones | Pass | Communication Requirements table maps each stakeholder to a milestone. | -| 5 | Conflicting stakeholder interests are identified with documented mitigation or resolution strategies | Pass | Four conflicts, each with stakeholders and a mitigation. | -| 6 | Stakeholder concerns are explicitly traced to Business Case objectives | Pass | Business Goal Alignment maps each concern to O1 to O4 of BC-001. | -| 7 | Primary concerns are expressed in both business language and a recognized quality-attribute mapping (e.g. FURPS+) | Pass | Primary Concern column plus a FURPS+ mapping table. | -| 8 | Document is understandable and navigable by non-technical stakeholders reviewing their own entry | Pass | Plain-language summary table and one section per topic. | - -## Overall Verdict - -Go — all eight criteria pass, with two follow-ups that do not affect the criteria. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. - -## Action Items - -| Action | Owner | Due | -| --- | --- | --- | -| Update the Sign-Off section, which still says 'Pending review by S01 and S05', with a Version History row | S01 | 2026-10-17 | -| Identify the holders of the S03 role (listed as 'holders to be confirmed') | S01 | 2026-10-17 | - ---- - -[SA-001]: ../../stakeholder-analysis.md -[QC-SA-001]: ../../../framework/qc/qc-stakeholder-analysis.md -[aa3f088]: https://git.tirsystem.com/TirSystem/github-action/commit/aa3f08876d55fa5f008e93f65176a496601c00ca +# Review Record: SA-001 Stakeholder Analysis + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-004 | +| CrossReference | [SA-001], [QC-SA-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | + +--- + +## Artifact Under Review + +- Instance reviewed: [SA-001] +- Checklist used: [QC-SA-001] + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | Power/Interest grid is filled for every stakeholder, with no gaps or unclassified entries | Pass | S01 to S05 each have Power, Interest and Quadrant. | +| 2 | Each stakeholder is assigned a unique, stable ID reusable for RACI assignments in other artifacts | Pass | IDs S01 to S05 are used by BC-001, PP-001 and the milestones. | +| 3 | Roles and organizational context are defined with explicit Power and Interest levels, not just narrative description | Pass | Role, organization and HIGH/MEDIUM/LOW levels per stakeholder, with a rationale section. | +| 4 | Communication needs (channel, frequency, deliverable type) are mapped to project phases or milestones | Pass | Communication Requirements table maps each stakeholder to a milestone. | +| 5 | Conflicting stakeholder interests are identified with documented mitigation or resolution strategies | Pass | Four conflicts, each with stakeholders and a mitigation. | +| 6 | Stakeholder concerns are explicitly traced to Business Case objectives | Pass | Business Goal Alignment maps each concern to O1 to O4 of BC-001. | +| 7 | Primary concerns are expressed in both business language and a recognized quality-attribute mapping (e.g. FURPS+) | Pass | Primary Concern column plus a FURPS+ mapping table. | +| 8 | Document is understandable and navigable by non-technical stakeholders reviewing their own entry | Pass | Plain-language summary table and one section per topic. | + +## Overall Verdict + +Go — all eight criteria pass, with two follow-ups that do not affect the criteria. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); the independent S05 review is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Update the Sign-Off section, which still says 'Pending review by S01 and S05', with a Version History row | S01 | 2026-10-17 | +| Identify the holders of the S03 role (listed as 'holders to be confirmed') | S01 | 2026-10-17 | + +--- + +[SA-001]: ../../stakeholder-analysis.md +[QC-SA-001]: ../../../framework/qc/qc-stakeholder-analysis.md +[aa3f088]: https://git.tirsystem.com/TirSystem/github-action/commit/aa3f08876d55fa5f008e93f65176a496601c00ca diff --git a/docs/sqa/reviews/rc-005-mil-002.md b/docs/sqa/reviews/rc-005-mil-002.md index 34c25c1..8ade06b 100644 --- a/docs/sqa/reviews/rc-005-mil-002.md +++ b/docs/sqa/reviews/rc-005-mil-002.md @@ -1,46 +1,46 @@ -# Review Record: MIL-002 - -## Metadata -| Key | Value | -| --- | --- | -| ID | RC-005 | -| CrossReference | [MIL-002], [QC-MIL-001] | - -## Version History -| Date | Status | Author | Reviewer | Change | Commit | -| --- | --- | --- | --- | --- | --- | -| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | - ---- - -## Artifact Under Review - -- Instance reviewed: [MIL-002] -- Checklist used: [QC-MIL-001] - -## Checklist Results - -| # | Criterion | Status | Evidence/Notes | -| --- | --- | --- | --- | -| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: verified onboarding and operations guide, credential validation step and categorized failure messages. | -| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Five criteria, each with an objectively checkable Go and No-Go column. | -| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-001, with the reason stated. | -| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-002 to O2 and O3 of BC-001. | -| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | -| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-10-31, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | - -## Overall Verdict - -Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. - -## Action Items - -| Action | Owner | Due | -| --- | --- | --- | -| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | - ---- - -[MIL-002]: ../../milestones/mil-002-onboarding-and-operations.md -[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md -[aa3f088]: https://git.tirsystem.com/TirSystem/github-action/commit/aa3f08876d55fa5f008e93f65176a496601c00ca +# Review Record: MIL-002 + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-005 | +| CrossReference | [MIL-002], [QC-MIL-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | + +--- + +## Artifact Under Review + +- Instance reviewed: [MIL-002] +- Checklist used: [QC-MIL-001] + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: verified onboarding and operations guide, credential validation step and categorized failure messages. | +| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Five criteria, each with an objectively checkable Go and No-Go column. | +| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-001, with the reason stated. | +| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-002 to O2 and O3 of BC-001. | +| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | +| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-10-31, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | + +## Overall Verdict + +Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); the independent S05 review is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | + +--- + +[MIL-002]: ../../milestones/mil-002-onboarding-and-operations.md +[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md +[aa3f088]: https://git.tirsystem.com/TirSystem/github-action/commit/aa3f08876d55fa5f008e93f65176a496601c00ca diff --git a/docs/sqa/reviews/rc-006-mil-003.md b/docs/sqa/reviews/rc-006-mil-003.md index d2e3133..42052fa 100644 --- a/docs/sqa/reviews/rc-006-mil-003.md +++ b/docs/sqa/reviews/rc-006-mil-003.md @@ -1,46 +1,46 @@ -# Review Record: MIL-003 - -## Metadata -| Key | Value | -| --- | --- | -| ID | RC-006 | -| CrossReference | [MIL-003], [QC-MIL-001] | - -## Version History -| Date | Status | Author | Reviewer | Change | Commit | -| --- | --- | --- | --- | --- | --- | -| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | - ---- - -## Artifact Under Review - -- Instance reviewed: [MIL-003] -- Checklist used: [QC-MIL-001] - -## Checklist Results - -| # | Criterion | Status | Evidence/Notes | -| --- | --- | --- | --- | -| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: a reusable quality-check workflow used by one other repository, and a results guide. | -| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Four criteria, each with an objectively checkable Go and No-Go column. | -| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-002, with the reason stated. | -| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-003 to O4 of BC-001. | -| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | -| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-11-14, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | - -## Overall Verdict - -Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. - -## Action Items - -| Action | Owner | Due | -| --- | --- | --- | -| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | - ---- - -[MIL-003]: ../../milestones/mil-003-quality-checks.md -[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md -[aa3f088]: https://git.tirsystem.com/TirSystem/github-action/commit/aa3f08876d55fa5f008e93f65176a496601c00ca +# Review Record: MIL-003 + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-006 | +| CrossReference | [MIL-003], [QC-MIL-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | + +--- + +## Artifact Under Review + +- Instance reviewed: [MIL-003] +- Checklist used: [QC-MIL-001] + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: a reusable quality-check workflow used by one other repository, and a results guide. | +| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Four criteria, each with an objectively checkable Go and No-Go column. | +| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-002, with the reason stated. | +| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-003 to O4 of BC-001. | +| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | +| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-11-14, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | + +## Overall Verdict + +Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); the independent S05 review is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | + +--- + +[MIL-003]: ../../milestones/mil-003-quality-checks.md +[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md +[aa3f088]: https://git.tirsystem.com/TirSystem/github-action/commit/aa3f08876d55fa5f008e93f65176a496601c00ca diff --git a/docs/sqa/reviews/rc-007-mil-004.md b/docs/sqa/reviews/rc-007-mil-004.md index bb13dfc..872db1b 100644 --- a/docs/sqa/reviews/rc-007-mil-004.md +++ b/docs/sqa/reviews/rc-007-mil-004.md @@ -1,46 +1,46 @@ -# Review Record: MIL-004 - -## Metadata -| Key | Value | -| --- | --- | -| ID | RC-007 | -| CrossReference | [MIL-004], [QC-MIL-001] | - -## Version History -| Date | Status | Author | Reviewer | Change | Commit | -| --- | --- | --- | --- | --- | --- | -| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | - ---- - -## Artifact Under Review - -- Instance reviewed: [MIL-004] -- Checklist used: [QC-MIL-001] - -## Checklist Results - -| # | Criterion | Status | Evidence/Notes | -| --- | --- | --- | --- | -| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: documented release process, consumer upgrade guide and a reusable release workflow. | -| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Four criteria, each with an objectively checkable Go and No-Go column. | -| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-003, with the reason stated. | -| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-004 to O4 of BC-001. | -| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | -| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-11-28, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | - -## Overall Verdict - -Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); independent review by S05 is recorded in RC-001 and applies here too. - -## Action Items - -| Action | Owner | Due | -| --- | --- | --- | -| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | - ---- - -[MIL-004]: ../../milestones/mil-004-versioned-release.md -[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md -[aa3f088]: https://git.tirsystem.com/TirSystem/github-action/commit/aa3f08876d55fa5f008e93f65176a496601c00ca +# Review Record: MIL-004 + +## Metadata +| Key | Value | +| --- | --- | +| ID | RC-007 | +| CrossReference | [MIL-004], [QC-MIL-001] | + +## Version History +| Date | Status | Author | Reviewer | Change | Commit | +| --- | --- | --- | --- | --- | --- | +| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | + +--- + +## Artifact Under Review + +- Instance reviewed: [MIL-004] +- Checklist used: [QC-MIL-001] + +## Checklist Results + +| # | Criterion | Status | Evidence/Notes | +| --- | --- | --- | --- | +| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable: documented release process, consumer upgrade guide and a reusable release workflow. | +| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Four criteria, each with an objectively checkable Go and No-Go column. | +| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies: depends on MIL-003, with the reason stated. | +| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability maps MIL-004 to O4 of BC-001. | +| 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05 and approving reviewer S01. | +| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target date 2026-11-28, marked proposed; the Business Case sets no deadline, so nothing contradicts it. | + +## Overall Verdict + +Go — all six criteria pass. Retrospective review prepared 2026-10-10 at the request of S01; the instance has been `Accepted` since 2026-10-03 and this record confirms it against the checklist. The author and the approving reviewer are the same person (S01); the independent S05 review is recorded in RC-001 and applies here too. + +## Action Items + +| Action | Owner | Due | +| --- | --- | --- | +| Confirm the proposed target date with S01 and S05 (the date is still marked proposed) | S05 | 2026-10-17 | + +--- + +[MIL-004]: ../../milestones/mil-004-versioned-release.md +[QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md +[aa3f088]: https://git.tirsystem.com/TirSystem/github-action/commit/aa3f08876d55fa5f008e93f65176a496601c00ca diff --git a/docs/sqa/traceability-matrix.md b/docs/sqa/traceability-matrix.md index e3f0ce7..ec6f99e 100644 --- a/docs/sqa/traceability-matrix.md +++ b/docs/sqa/traceability-matrix.md @@ -9,7 +9,8 @@ ## Version History | Date | Status | Author | Reviewer | Change | Commit | | --- | --- | --- | --- | --- | --- | -| 2026-10-10 | Proposed | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | +| 2026-10-10 | Deprecated | Jens Tirsvad Nielsen | S05 | Initial version | [aa3f088] | +| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S05 | S05 review approved (reported by S01)
Review records RC-001 to RC-007 are Accepted | pending | --- @@ -43,7 +44,7 @@ updated whenever an artifact instance is created or reviewed. - `-` in Upstream means foundational (SA-001 has no prerequisite). In Downstream it means nothing is built on the instance yet. In Last Reviewed it means no `RC-*` exists (review records are not themselves reviewed). - Types with no instance yet: KPI, BMC, BPMN, UCD, US, UC, SSD, DM, OC, SD, DCD, ERD, ADR, GOV, DICT. The Project Plan lists use case candidates, but the formal use cases wait for a use case diagram and user stories. - PP-001 and TM-001 have no QC checklist; RC-002 validated PP-001 against its Business Case constraints and the milestone Go / No-Go criteria. TM-001 has no review record. -- All review records are `Proposed`; the author and S01 are the same person, so an independent review by S05 is outstanding (see RC-001). +- All review records are `Accepted` after the S05 review (reported by S01 on 2026-10-10); the author and S01 are the same person, so S05 is the independent reviewer. ---