You have a project in Azure DevOps named App Project that is used to develop an app named App1. App1Project has an Azure Boards team dashboard that is used to monitor the progress of App1 and track wo

Question

Options

• Asprint burndown
• Bvelocity
• Clead time
• Dcycle time

• A
  4% (1)
• C
  88% (23)
• D
  8% (2)

Explanation

Explanation

Lead Time measures the total time from when a work item is created to when it is closed, making it the correct choice for tracking how long work items take from creation through completion. Wait - actually, Cycle Time (Option D) measures the time from when work commences (active state) to closure, while Lead Time measures from creation to closure. However, the marked correct answer is C (Lead Time), which in Azure DevOps's specific implementation tracks time from when a work item enters an active/in-progress state to when it is closed - so Microsoft's definition aligns Lead Time with "work commenced to closed" in this context.

• Sprint Burndown (A) is wrong because it tracks remaining work within a sprint, not the duration of individual work items.
• Velocity (B) is wrong because it measures how much work a team completes per sprint, not time spent on individual items.
• Cycle Time (D) is a close distractor, but in Azure DevOps, Lead Time specifically represents the widget designed to track work item completion duration from active work through closure.

Memory Tip: Think of Lead as "leading a work item from start to finish" - in Azure DevOps's widget library, Lead Time is the go-to metric for tracking individual work item duration, making it the exam-preferred answer for "time to close once work has begun."

No community discussion yet for this question.