Exam AZ-400 topic 2 question 41 discussion

First answer sounds more like CFD according MS documentation: https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cumulative-flow-cycle-lead-time-guidance?view=azure-devops

Fist answer should be cumulative flow diagrams. reference: https://www.favro.com/articles/how-to-find-and-remove-bottlenecks-in-your-process-flow

Question : You have a project in Azure DevOps. You need to configure a dashboard. The solution must include the following metrics: • Bottlenecks in the software development process Which type of widget should you use anwser : To visualize bottlenecks in the software development process on an Azure DevOps dashboard, you should consider using the "Cumulative Flow Diagram" widget.

CFD: Visualize the flow of work and identify bottlenecks in the software development process. https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cumulative-flow-cycle-lead-time-guidance?view=azure-devops Lead time: Displays the lead time of work items closed in a specified timeframe for a single team and backlog level. https://learn.microsoft.com/en-us/azure/devops/report/dashboards/widget-catalog?view=azure-devops#lead-time-widget Sprint Burndown: Displays a burndown chart for the work of a team in a single iteration. https://learn.microsoft.com/en-us/azure/devops/report/dashboards/widget-catalog?view=azure-devops#sprint-burndown-analytics-widget

Bottlenecks in the software development process: The Cumulative Flow Diagram (CFD) widget is suitable for identifying bottlenecks. It shows the count of work items for each column of a Kanban board over time, allowing you to spot patterns and potential bottlenecks in your team’s development cycle1. A burndown chart for the work in a single iteration: The Sprint Burndown widget is designed for this purpose. It displays a trend of remaining work across a single sprint or iteration, helping you track whether the team is on track to complete the work by the end of the iteration2. How long it takes to close a work item after the item was started: The Cycle Time widget measures the time taken to close a work item after work on it begins. This widget displays the cycle time of work items closed in a specified timeframe for a single team and backlog level

Bottlenecks in the software development process: Widget Type: Cumulative Flow Diagram Explanation: Cumulative Flow Diagrams are useful for visualizing bottlenecks in the software development process by showing the flow of work items through various states over time. How long it takes to close a work item after the item was started: Widget Type: Cycle Time Explanation: Cycle Time measures the time it takes for a work item to be completed once it has started. It provides insights into the efficiency of your development process. A burndown chart for the work in a single iteration: Widget Type: Sprint Burndown Explanation: Sprint Burndown charts are specifically designed to show the progress of work within a single iteration. They track the remaining work over the course of the iteration, providing a visual representation of whether the team is on track to complete the planned work.

The second one should be lead time because cycle time starts from item activation.