AzDo - AzDo | [Copilot integration] report/dashboards/configure-sprint-burndown.md

Author: RoseHJM

docs/report/dashboards/configure-sprint-burndown.md

@@ -2,7 +2,7 @@
 title: Configure and monitor sprint burndown
 titleSuffix: Azure DevOps
 description: Learn how to configure and monitor sprint burndown charts in Azure DevOps to track team progress and ensure your sprint plan stays on track.
-ms.custom: dashboards, copilot-scenario-highlight
+ms.custom: dashboards, copilot-scenario-highlight, awp-ai
 ms.subservice: azure-devops-analytics
 ms.author: chcomley
 author: chcomley
@@ -212,6 +212,8 @@ If your sprint burndown chart appears empty, check these points:
 
 ::: moniker range="azure-devops"
 
+<a id="use-ai-monitor-sprint-burndown">  </a>
+
 ## Use AI to monitor sprint burndown
 
 If you configure the [Azure DevOps MCP Server](/azure/devops/mcp-server/mcp-server-overview), you can use AI assistants to help configure and interpret sprint burndown charts.
@@ -220,15 +222,18 @@ If you configure the [Azure DevOps MCP Server](/azure/devops/mcp-server/mcp-serv
 
 | Task | Example prompt |
 |------|----------------|
-| Configure the report | `Help me set up a sprint burndown widget that tracks Remaining Work for my team's current sprint in <Contoso> project` |
-| Interpret the chart | `My sprint burndown shows a flat line for the first 3 days — what does that indicate and what should my team do?` |
-| Compare approaches | `What's the difference between the in-context sprint burndown report and the Sprint Burndown widget? Which should I use?` |
-| Track by story points | `Help me configure sprint burndown by Story Points instead of work item count in <Contoso> project` |
-| Retrospective insights | `Based on sprint burndown patterns, what process improvements should my team discuss in our retrospective?` |
-| Scope changes | `How can I tell from the sprint burndown chart whether scope was added mid-sprint?` |
-| Predict risk early | `Our sprint burndown is flat after day 3 of a 10-day sprint — what's the likelihood we'll finish on time and what should we adjust?` |
-| Compare sprints | `Compare our last three sprint burndown patterns and identify whether our estimation accuracy is improving` |
-| Optimize sprint length | `Based on our burndown history, would our team benefit from shorter two-week sprints instead of three-week sprints?` |
+| View the report | `Open the in-context sprint burndown report for <team> in <project> (<organization>) and explain what I'm seeing` |
+| Configure the widget | `Help me set up a Sprint Burndown widget on the <dashboard> dashboard for <team> in <project> (<organization>) that burns down Remaining Work` |
+| Troubleshoot an empty chart | `My sprint burndown chart is empty for <team> in <project> (<organization>) — walk me through what to check (iterations, tasks, Remaining Work, and parent items)` |
+| Track by story points | `Help me configure sprint burndown by Story Points for <team> in <project> (<organization>) and explain any prerequisites` |
+| Interpret a flat burndown | `In sprint <sprint-name>, our burndown is flat for the first <n> days — what does that usually indicate, and what should <team> do next?` |
+| Identify scope changes | `In the sprint burndown for <team> in <project> (<organization>), how do I tell whether scope was added mid-sprint and when it happened?` |
+| Compare report vs widget | `What's the difference between the in-context Burndown Trend report and the Sprint Burndown widget in Azure DevOps, and when should <team> use each?` |
+| Compare sprints | `Compare the last <n> sprints for <team> in <project> (<organization>) using burndown patterns and summarize whether our estimation accuracy is improving` |
+| Prepare for a retrospective | `Based on the last sprint burndown for <team> in <project> (<organization>), suggest 3 retrospective questions and 3 process improvements to discuss` |
+
+> [!TIP]
+> If you're using Visual Studio Code, agent mode is especially helpful for iterating on multi-step analysis (for example, comparing burndown trends across multiple sprints and summarizing the takeaways).
 
 ::: moniker-end