AZ-400 Question 19
Select 2Your organization uses Azure Boards in Azure DevOps to track user stories, tasks, and bugs. You have been asked to build a dashboard that measures how long work items spend in development (cycle time), how quickly the team recovers from production incidents (time to recovery), and how long it takes from request to deployment (lead time). Which two actions should you perform as part of designing the dashboard in Azure DevOps to track these metrics effectively?
- A
Use Analytics Views or the built-in Work Item Analytics to measure end-to-end durations for each item, calculating lead time from creation to closure.
- B
Rely solely on the Cumulative Flow Diagram to measure time to recovery by referencing production environment logs.
- C
Configure a Cycle Time or Lead Time widget that references 'Active' or 'In Progress' states to measure how long a work item remains under development.
- D
Implement a pinned build summary widget to measure time to recovery, ignoring work item state transitions or deployment logs.
Show answer and explanation
Correct answers: A, C
Explanation
In Azure DevOps, accurately measuring flow of work (cycle time, lead time, and time to recovery) requires using the right analytics tools and widgets. Cycle and lead time can be tracked through Work Item Analytics, Analytics Views, or dedicated widgets that measure how long a work item spends in each relevant state. Time to recovery typically requires tracking production incident details and ensuring that your dashboard references relevant evidence from deployment logs, QA validations, or incident management data. Reference: Microsoft� official Azure DevOps documentation on analytics and reporting (https://docs.microsoft.com/azure/devops/report/?view=azure-devops).
- A. Correct.
Correct. Analytics Views or the built-in Work Item Analytics can be customized to filter by creation and completion dates, giving you accurate lead time metrics from inception to done. This approach aligns with Azure DevOps best practices for measuring end-to-end durations.
- B. Incorrect.
Incorrect. The Cumulative Flow Diagram measures the flow of work items across states, not the actual production incident data or logs. While it helps visualize bottlenecks or state transitions, it is not the right tool to measure direct time to recovery from production issues.
- C. Correct.
Correct. Cycle Time and Lead Time widgets in Azure DevOps can be configured to track how long work items remain in specific states (e.g., 'Active' or 'In Progress'). This setup accurately reflects how long your team spends actually coding or developing the feature before moving it to closed or resolved states.
- D. Incorrect.
Incorrect. A pinned build summary widget only displays build status and durations of specific builds. It does not provide end-to-end time to recovery insights, as it ignores incident context, work item state transitions, and deployment logs, all of which are crucial for measuring time to recovery.