microsoft/hve-core
Publicmirrored fromhttps://github.com/microsoft/hve-coreAvailable
docs/agents/github-backlog/sprint-planning.md
122lines · modecode
| 1 | --- |
| 2 | title: Sprint Planning Workflow |
| 3 | description: Organize triaged issues into milestones with priority sequencing and capacity awareness |
| 4 | sidebar_position: 5 |
| 5 | author: Microsoft |
| 6 | ms.date: 2026-02-12 |
| 7 | ms.topic: tutorial |
| 8 | keywords: |
| 9 | - github backlog manager |
| 10 | - sprint planning |
| 11 | - milestones |
| 12 | - github copilot |
| 13 | estimated_reading_time: 5 |
| 14 | --- |
| 15 | |
| 16 | The Sprint Planning workflow organizes triaged issues into milestones, sequences work by priority, and produces execution-ready handoff files that map issues to their target sprint. |
| 17 | |
| 18 | ## When to Use |
| 19 | |
| 20 | * 📅 Starting a new sprint or release cycle and need to assign issues to milestones |
| 21 | * 🎯 Issues have been triaged but lack milestone assignments |
| 22 | * 🔄 Rebalancing work across milestones after scope changes or team adjustments |
| 23 | * 📋 Creating milestone structure for a new project or repository |
| 24 | |
| 25 | ## What It Does |
| 26 | |
| 27 | 1. Reads triage output to understand issue classification and priority levels |
| 28 | 2. Discovers existing milestones or recommends new ones based on issue patterns |
| 29 | 3. Maps issues to milestones considering priority, dependencies, and grouping |
| 30 | 4. Sequences work within each milestone based on priority assessment and blocking relationships |
| 31 | 5. Produces a sprint plan with milestone assignments and a handoff file for execution |
| 32 | |
| 33 | > [!NOTE] |
| 34 | > Sprint planning does not create milestones automatically. It recommends milestone assignments in a handoff file that the execution workflow applies after your review. |
| 35 | |
| 36 | ## Milestone Discovery |
| 37 | |
| 38 | The workflow follows a structured approach to milestone management: |
| 39 | |
| 40 | 1. Queries the repository for existing open milestones with due dates |
| 41 | 2. Maps triaged issues to milestones by area label and priority |
| 42 | 3. Identifies issues that fit no current milestone and recommends creating new ones |
| 43 | 4. Checks milestone capacity using issue count and priority distribution |
| 44 | 5. Flags milestones that appear overloaded relative to their due date |
| 45 | 6. Produces a milestone map showing current and recommended assignments |
| 46 | |
| 47 | This process ensures sprint plans build on existing repository structure rather than creating parallel tracking systems. |
| 48 | |
| 49 | ## Output Artifacts |
| 50 | |
| 51 | ```text |
| 52 | .copilot-tracking/github-issues/sprint/<milestone-kebab>/ |
| 53 | ├── sprint-analysis.md # Milestone mapping and capacity review |
| 54 | ├── sprint-plan.md # Recommended assignments and sequencing |
| 55 | └── handoff.md # Execution-ready handoff with checkboxes |
| 56 | ``` |
| 57 | |
| 58 | The sprint plan includes reasoning for each milestone assignment, making it possible to adjust recommendations before execution applies them. |
| 59 | |
| 60 | ## How to Use |
| 61 | |
| 62 | ### Option 1: Prompt Shortcut |
| 63 | |
| 64 | ```text |
| 65 | Plan the next sprint for microsoft/hve-core using my latest triage results |
| 66 | ``` |
| 67 | |
| 68 | ```text |
| 69 | Assign milestones to all triaged issues without milestone assignments |
| 70 | ``` |
| 71 | |
| 72 | ### Option 2: Direct Agent |
| 73 | |
| 74 | Start a conversation with the GitHub Backlog Manager agent and reference your triage output. The agent reads the triage analysis and handoff files, then builds a sprint plan based on current milestone structure. |
| 75 | |
| 76 | ## Example Prompt |
| 77 | |
| 78 | ```text |
| 79 | Plan sprint assignments for microsoft/hve-core. Use the v2.1 milestone for |
| 80 | high-priority bugs and the v2.2 milestone for enhancements. Create a new |
| 81 | "documentation-refresh" milestone for any docs-area issues without a milestone. |
| 82 | ``` |
| 83 | |
| 84 | ## Tips |
| 85 | |
| 86 | ✅ Do: |
| 87 | |
| 88 | * Run triage before sprint planning so issues have consistent labels and priorities |
| 89 | * Review milestone capacity recommendations before approving assignments |
| 90 | * Use the sequencing output to identify blocking chains within a milestone |
| 91 | * Adjust milestone assignments in the handoff file before passing to execution |
| 92 | |
| 93 | ❌ Don't: |
| 94 | |
| 95 | * Plan sprints without triaged issues (issues that lack triage metadata produce unreliable plans) |
| 96 | * Ignore capacity warnings for milestones approaching their due date |
| 97 | * Create milestones through sprint planning when they should be created through repository settings |
| 98 | * Assume the workflow sees private milestones (verify MCP token permissions) |
| 99 | |
| 100 | ## Common Pitfalls |
| 101 | |
| 102 | | Pitfall | Solution | |
| 103 | |----------------------------------------|-------------------------------------------------------------------------| |
| 104 | | Issues assigned to closed milestones | The workflow flags these for reassignment; review before execution | |
| 105 | | Milestone names don't match repository | Verify milestone names in the handoff match existing milestones exactly | |
| 106 | | Priority conflicts within a milestone | Review the sequencing recommendations and adjust priority labels first | |
| 107 | | Too many issues for a single milestone | Split across milestones or re-prioritize lower-priority items out | |
| 108 | |
| 109 | ## Next Steps |
| 110 | |
| 111 | 1. Review the sprint plan and handoff file for accuracy |
| 112 | 2. Proceed to the [Execution workflow](execution.md) to apply milestone assignments |
| 113 | |
| 114 | > [!TIP] |
| 115 | > For teams with fixed sprint cadences, create milestones in advance through repository settings. Sprint planning works best when it maps to existing milestones rather than recommending new ones. |
| 116 | |
| 117 | --- |
| 118 | |
| 119 | <!-- markdownlint-disable MD036 --> |
| 120 | *🤖 Crafted with precision by ✨Copilot following brilliant human instruction, |
| 121 | then carefully refined by our team of discerning human reviewers.* |
| 122 | <!-- markdownlint-enable MD036 --> |
| 123 | |