Criterion 6
Delivery audit trail
Ratings 2026-10
A retained record identifies the delivered build and changes, governing requirement and design versions, reviews, approvals and waivers. It references the applicable test results.
Coverage levels
- Level 1 Review, baseline or check evidence concerns a specific change; complete delivery/build association is missing.
- Level 2 Build-linked change, test and review evidence exists; governing design or approval/waiver association remains incomplete.
- Level 3 A delivered build identifies its changes, governing requirement/design versions, reviews, approvals/waivers and applicable result references.
Product ratings
Issues, pull requests, commits, reviews and check logs identify changes and decisions.
Read the rating and evidence
Work items, commits, PRs, builds, test records and configured approvals provide substantial delivery evidence.
Read the rating and evidence
Jira keys, PR reviews and Confluence history provide parts of the audit trail.
Read the rating and evidence
Git can retain feature specs with code.
Read the rating and evidence
Git retains specification and implementation history.
Read the rating and evidence
Current specs and archived change records can accompany code in Git.
Read the rating and evidence
Plans, baseline references, dated reviews and retrospectives give partial provenance.
Read the rating and evidence
Versioned specs and implementation, plus retained PR verifier checks, provide partial provenance.
Read the rating and evidence
Baselines, signed reviews, item history and referenced test results support audit.
Read the rating and evidence
Collections, LiveDocs history, signatures, code links and test records preserve audit evidence.
Read the rating and evidence
PR changes, QA reports, evidence artifacts and review records identify a checked change.
Read the rating and evidence
Back to comparison