# Code Review Checklist — Implementation Workbook Version: 1.0 Published: 2026-07-27 Last updated: 2026-07-27 Owner: Rusaka Research Review frequency: Every 6 months ## Decision statement What decision must this workbook support? ________________________________________________________________________________ ## Scope and exclusions In scope: ________________________________________________________________________________ Out of scope: ________________________________________________________________________________ ## Baseline evidence register | Evidence item | Source | Date | Owner | Verified by | Status | |---|---|---|---|---|---| | | | | | | | | | | | | | | | | | | | | | ## Assumption register | Assumption | Rationale | Decision affected | Downside case | Test | Owner | Review date | |---|---|---|---|---|---|---| | | | | | | | | | | | | | | | | ## Options and decision criteria | Option | Outcome | Feasibility | Cost | Time | Risk | Reversibility | Recommendation | |---|---:|---:|---:|---:|---:|---:|---| | | | | | | | | | | | | | | | | | | ## Implementation plan | Phase | Entry evidence | Actions | Owner | Control | Exit evidence | Due date | |---|---|---|---|---|---|---| | 1. Scale — Code Review Checklist | | During scale, use Code Review Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | | | 2. Operations — Code Review Checklist | | During operations, use Code Review Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | | | 3. Discovery — Code Review Checklist | | During discovery, use Code Review Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | | | 4. Design — Code Review Checklist | | During design, use Code Review Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | | | 5. Pilot — Code Review Checklist | | During pilot, use Code Review Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | | ## Measures and thresholds | Measure | Definition | Source | Baseline | Target | Threshold | Owner | Frequency | |---|---|---|---:|---:|---:|---|---| | | | | | | | | | | | | | | | | | | ## Risk and control register | Risk | Cause | Impact | Preventive control | Detective control | Owner | Residual risk | |---|---|---|---|---|---|---| | | | | | | | | | | | | | | | | ## Review checklist - [ ] 1. Scale readiness: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 2. Review and renewal: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 3. Decision boundary: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 4. Stakeholder map: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 5. Current-state baseline: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 6. Evidence design: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 7. Operating model: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 8. Architecture and integration: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 9. Risk and compliance: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 10. Economics and value: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 11. Delivery sequencing: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 12. Vendor and partner assessment: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 13. Measurement system: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. - [ ] 14. Quality assurance: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear. ## Approval record | Role | Name | Decision | Conditions | Date | |---|---|---|---|---| | Accountable owner | | | | | | Subject-matter reviewer | | | | | | Risk or control reviewer | | | | | ## Authoritative references - https://www.w3.org/TR/ — Authoritative reference 1 for the evidence and standards relevant to Software Engineering. Confirm the current version and applicability before relying on it. - https://www.rfc-editor.org/ — Authoritative reference 2 for the evidence and standards relevant to Software Engineering. Confirm the current version and applicability before relying on it. - https://docs.github.com/ — Authoritative reference 3 for the evidence and standards relevant to Software Engineering. Confirm the current version and applicability before relying on it. ## Related Rusaka resources - https://www.rusaka.com/resources/checklists - https://www.rusaka.com/resources/guides/testing-strategy - https://www.rusaka.com/resources/guides/technical-debt-guide - https://www.rusaka.com/resources/checklists/ai-implementation-checklist - https://www.rusaka.com/resources/checklists/due-diligence-checklist - https://www.rusaka.com/resources/calculators/software-cost-calculator - https://www.rusaka.com/resources/templates/software-estimation-template - https://www.rusaka.com/resources/guides/software-development-guide ## Important limitation This educational workbook does not replace legal, investment, tax, accounting, security, clinical, regulatory, or other qualified professional advice. Confirm current requirements and obtain formal organisational approval where applicable.