Microsoft Certified: DevOps Engineer ExpertConfigure processes and communicationsEasy
A DevOps team is managing an Azure DevOps project. They want to ensure that all work items related to a specific product backlog item (PBI) are automatically linked when new tasks or bugs are created from that PBI. This will help in maintaining traceability and understanding the complete scope of work. Which linking type should the team configure as the default for new work item creations from a PBI?
- ASuccessor
- BRelated
- CChild
- DPredecessor
Show answer & explanationAnswer & explanation
Correct answer: C. Child
When creating new work items like tasks or bugs from a Product Backlog Item (PBI), the 'Child' link type is the most appropriate to establish a hierarchical relationship, ensuring traceability and representing that the tasks/bugs are components of the PBI.
Why the other options are wrong
- A. The 'Successor' link type indicates that one work item must start after another is completed, also a dependency, not a hierarchical breakdown of a PBI.
- B. The 'Related' link type indicates a general association but does not imply a hierarchical or dependency relationship, making it less suitable for representing sub-items of a PBI.
- D. The 'Predecessor' link type indicates that one work item must be completed before another can start, which is a dependency, not a hierarchical breakdown of a PBI.
Work Item Linking Hierarchy
Work item linking in Azure DevOps establishes relationships between work items for traceability, dependency management, and hierarchical organization. 'Child' links are used for breaking down larger work into smaller, manageable pieces.
- Establishes relationships between work items.
- Supports traceability and dependency tracking.
- Common types include Parent/Child, Related, Predecessor/Successor.
Memory trick: Links form a family tree for work.