When to use it
A useful fit
Use it when several rules, contracts or policies affect scope and the team needs to show how each is being met.
Know the limits
Do not rank legal force from a generic template. A voluntary commitment or code can become contractually binding; ask the relevant specialist.
How to use it
- Identify each obligation, its actual source, applicability and review owner.
- Connect it to a requirement, control or acceptance check.
- Maintain dated evidence and revisit the map when the rule, contract or design changes.
Worked example
A service launch has contractual support hours and an internal data-retention policy. The delivery lead records separate owners and acceptance evidence for each. A policy question is sent to the appropriate specialist before deletion behaviour is built.
Illustrative scenario by fannarmaximus; not an official exam question.
Common pitfalls
Labelling something voluntary is not evidence that it can be ignored.
Attribution & sources
The map is an original organising tool by fannarmaximus. It is not legal advice or a substitute for qualified interpretation.
The citations below identify authoritative references for this topic. They do not imply endorsement or reproduce the bodies’ competence lists.
- IPMA® (2015). Individual Competence Baseline for Project, Programme and Portfolio Management, Version 4.0 (ICB4). Zurich: International Project Management Association. ISBN 978-94-92338-00-6 (print), 978-94-92338-01-3 (pdf). Free PDF from IPMA®: https://ipma.world/ipma-standards-development-programme/icb4/
- Association for Project Management (2025). APM Body of Knowledge, 8th edition. Princes Risborough: APM. ISBN 9781913305390.