Work item tracking - AV
This page describes work item tracking in AV and helps to answer questions, such as:
- How can we track work items in AV?
- From a System point of view - with a focus on expected deliverables
- From the AV point of view - with a focus on execution
- How can Systems monitor the progress of the functionalities they are expecting from AV?
- How can we show tests, test coverage, and bug fixes?
- How can we build dashboards to show this information?
Backlog levels and area path mapping
AV backlog levels can be defined following the backlog levels described in the QMS and mapped to SAFe Agile. System, AV Release Owner, and AV Development Teams can track work items from their backlog in Azure DevOps.
| Backlog level | Items | Area Path | Description |
|---|---|---|---|
| System | System Epic | [ADO Project Name]\PCP Work\[System]…\[System rev.] Example: [ADO Project Name]\PCP Work\System 800xA\7.0\7.0.0 | System Epics imported from DFN as basis for AV development |
| AV Project | Epic | [ADO Project Name]\Development Stream\[Project]…\[Component Sub Ver.] Example: PCP\Engineering\NGT_Engg\CertificateDashboard\2.0\2.0.0 | Epics planned for AV, delivered in Target System Releases |
| AV team | Feature User Story (Bug) | [ADO Project Name]\Development Stream\[Project]\…\[Component Sub Ver.] Example: PCP\Engineering\NGT_Engg\CertificateDashboard\2.0\2.0.0 | Detailed work items the AV team plans and executes |
Target System Release
To be able to easily visualize the relationship between work items planned for AV components and the receiving System(s), we are introducing a custom field called "Target System Release". This makes it easier for users to get this information without having to navigate the work item tree structure and also simplifies the creation of queries and dashboards for better transparency and traceability.
How does it work?
- The area path of AV work items will contain the AV component and its version ONLY, not the target system.
- The relationship between Epics and the target System is visible through the custom field Target System Release set in Epic work items and Bug work items.
- Target System Release is a multi-value custom field and is more reliable and consistent than tags. One or multiple values can be selected from the available ones.
- Target System Release is propagated automatically from Epic to its Features and Stories descendants.
- System expects work items based on Target System Release
- AV delivers components defined by the component area path
- For bugs, Target System Release can be considered an extension of Area Path and show where the bug exists. The state/reason is further information about the plan and implementation.
For example, 800xA 7.0 xP1 and SPlus Phoenix could be selected together. 800xA 7.0 xP0 and 800xA 7.0 xP1 together would not be meaningful.
How to: Work item management for multiple releases
Bug routing
Key concepts:
- AV Bugs need to be created in the AV project and area path
- System Build can be specified in System Info
- Target System Release is where it's planned to be fixed
- Bug fix integrated into AV project deliverable and described in build notes for validation at the system level
Examples: Bug Queries
| Query | Implementation |
|---|---|
| Work items from a fixed baseline | ID in <Work item ID1, Work item ID1> |
| Scope Bugs in a component | Area path = PCP\Engineering\NGT_Engg\Dashboard\2.0\2.0.0 Scope Bug = True |
| Test Bugs in a component | Area path = PCP\Engineering\NGT_Engg\Dashboard\2.0\2.0.0 Scope Bug = False |
| Test Bugs found in a Target System Release, belonging to a specific component | Area path = PCP\Engineering\NGT_Engg\Dashboard\2.0\2.0.0 Scope Bug = False Target System release = 800xA 7.0 xP0 |
| Deferred Test Bug from the current release, belonging to a specific component (original bug) | Area path = PCP\Engineering\NGT_Engg\Dashboard\2.0\2.0.0 State = Closed Reason = Deferred Target System release = 800xA 7.0 xP0 |
| Scope bugs to be fixed in a Target System Release, belonging to a specific component (cloned bug) | Area path = PCP\Engineering\NGT_Engg\Dashboard\3.0\3.0.0 Scope Bug = True Cloned = True Target System release = 800xA 7.0 xP1 (next release) |
Examples: Dashboard
Example of a Dashboard that can be built with this work item tracking model: https://dev.azure.com/ABB-BCI-PCP/PCP-Test/_dashboards/dashboard/4fba0591-ab2e-4963-9ff9-f43d8e42fa4b (Note, this example illustrates how to get data to build a dashboard. After the implementation of the model, this link will be replaced by the actual dashboard.)