Integration · Candidate · delivery-method integration
ArtiProof × Scrum
Add knowledge checkpoints to existing Scrum events and artefacts without changing Scrum itself.
Candidate mapping. No endorsement, equivalence, certification transfer or conformity is implied.
What the host method already does
Scrum is defined in the Scrum Guide; the current official guide remains the November 2020 version.
Where knowledge matters
- Product Backlog refinement and product knowledge
- Sprint Review when new system behaviour changes knowledge
- Sprint Retrospective when team capability or dependency changes
- Definition-of-Done-adjacent local checks where knowledge evidence matters
Proposed addition
- key-person and Generated Knowledge dependency questions
- provenance and authority checks for consequential outputs
- knowledge recovery thinking around team or supplier change
- a decision on whether extra evidence is proportionate
Evidence that may be reusable
- Product Backlog and Sprint Backlog items
- Increment and review evidence
- retrospective learning
- team working agreements and technical documentation
How could this work?
Host method
Start with an existing meeting, document or review in the method you use.
→
ArtiProof checkpoint
Focus on knowledge questions that could affect the decision or next step.
Host-method reference snapshot
Reference snapshot checked 23 August 2026: official current Scrum Guide is November 2020.
Help develop this integration
Help us identify what the existing method already covers, what evidence is available and where an extra question might help. We also want to know where ArtiProof simply duplicates work.