Work Product Traceability
This guide describes traceability between work products that are not in Azure DevOps (ADO).
Intended for
Product owners, configuration managers, release owners, scrum masters, product managers, and quality control managers.
Traceability
To ensure consistency, traceability between key work products is essential. Traceability between work products defined as ADO work items is implemented with different links (parent, child, etc.). Traceability between work products that are not work items in ADO, such as architecture or product capabilities in markdown stored in ADO, or release notes in Word, needs to be established through other mechanisms.
This figure gives an overview of work product traceability:
Below follows a description of how traceability is established between key work products.
Work item traceability in ADO
Covered by separate guide: Work Item Traceability.
Epic and architecture
- An epic includes a pull request link to the updated architecture.
- The architectural history shows which epic contributed to what changes.
Epic and product capability
- An epic includes a pull request link to the updated product capability.
- The product capability history shows which epic contributed to what changes.
Product capability and architecture
- The structure of product capability and architecture shall follow the same naming conventions.
Product capability and product test
- An epic includes a pull request link to the updated product capability. The epic also includes a link to the impacted test cases.
- The product tests are grouped according to the product capabilities.