Bitzu

AZ-400 ยท DevOps metrics and dashboards

Flow metrics and dashboards in Azure DevOps

Lead time, cycle time, time to recovery, change failure rate, deployment frequency, cumulative flow and velocity widgets; Azure DevOps dashboards and Analytics views; what each metric tells you.

Key points

  • Lead time: work item creation to completion. Cycle time: work start to completion.
  • Lead Time and Cycle Time widgets: scatter charts, moving average, standard deviation band.
  • Cumulative flow diagram: item counts per state over time (bulges = bottlenecks, flat lines = stalled updates).
  • Velocity: work completed per sprint.
  • DORA-style: deployment frequency, change failure rate, time to restore service.

Source: https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cumulative-flow-cycle-lead-time-guidance?view=azure-devops

Practice questions

Single choice

In Azure DevOps, which interval does lead time measure for a work item?

  1. From creation until it reaches a Completed state
  2. From first In Progress until it reaches a Completed state
  3. From sprint start until sprint end
  4. From deployment until the first incident
Show answer

Answer: A. From creation until it reaches a Completed state

Lead time starts at creation and ends in a Completed state category. Cycle time is the one that starts when work begins.

Select all that apply

Which measures are commonly used to describe software delivery performance (DORA-style)?

  1. Deployment frequency
  2. Change failure rate
  3. Time to restore service
  4. Sprint velocity in story points
  5. Percentage of code covered by unit tests
Show answer

Answer: A. Deployment frequency, B. Change failure rate, C. Time to restore service

Deployment frequency, change failure rate and time to restore service describe delivery performance. Velocity and code coverage are team/quality measures, not delivery-performance outcomes.

True or false

True or false: In Azure DevOps velocity, an item planned for Sprint 1 but finished during Sprint 3 counts toward Sprint 1's velocity.

Show answer

Answer: False

Velocity credit goes to the sprint in which the item is completed (Sprint 3); the item still counts as planned for Sprint 1.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More AZ-400 topics in this module