Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
Azure DevOps Services | Azure DevOps Server | Azure DevOps Server 2022
After you define tasks for your sprint backlog items, check the team's capacity. Add items if the team is under capacity, or remove items if over capacity. Then check individual capacity bars to see if any team member is overloaded or has no work assigned. If you haven't set capacity yet, do that first.
Prerequisites
| Category | Requirements |
|---|---|
| Project access | Project member. |
| Permissions | - Member of the Contributors or Project Administrators security group. - To view or modify work items: View work items in this node and Edit work items in this node permissions set to Allow. By default, the Contributors group has this permission set to Allow. For more information, see Set work tracking permissions. |
| Access levels | To add or modify work items: At least Basic access. Users with Stakeholder access for public projects have full access to backlog and board features, like users with Basic access. For more information, see Stakeholder access quick reference. |
| Defined iterations | To use the Planning pane: Ensure your team administrator defined iteration paths (sprints) and configure team iterations. |
| Category | Requirements |
|---|---|
| Project access | Project member. |
| Permissions | - Member of the Contributors or Project Administrators security group. - To view or modify work items: View work items in this node and Edit work items in this node permissions set to Allow. By default, the Contributors group has this permission set to Allow. For more information, see Set work tracking permissions. |
| Access levels | To add or modify work items: At least Basic access. |
| Defined iterations | To use the Planning pane: Ensure your team administrator defined iteration paths (sprints) and configure team iterations. |
Tip
You can use AI to help with this task later in this article, or see Enable AI assistance with Azure DevOps MCP Server to get started.
Open a sprint backlog for a team
From your project, select Boards > Sprints, select your team, and then select Backlog.
To switch teams, open the team selector and choose a different team, or select the
Browse all sprints option. You can also enter a keyword to filter the list.
To switch sprints, open the sprint selector and choose the sprint you want.
Only sprints selected for the current team appear. If the sprint you need isn't listed, select New Sprint > Select existing iteration. For more information, see Define iteration (sprint) paths.
Check your team capacity
Turn on Work details to view capacity charts for the sprint.
Move items out of a sprint
If your team is over capacity, move items back to the product backlog or into the next sprint. All child tasks move with the backlog item. Moving to the backlog resets the Iteration Path to the team default.
Select the items to move, open the 
actions menu, choose Move to iteration, and then select Backlog.
Tip
You can also open the Planning pane and drag items to the backlog or another sprint — child tasks move automatically. Multi-select is supported. Users with Stakeholder access can't drag and drop work items. For more information, see Assign work to a sprint.
Balance work across the team
To reassign tasks, drag a task onto the new assignee's capacity bar. Capacity bars update automatically.
The following example reassigns work from Raisa Pokrovskaya to Christie Church.
Use AI to adjust sprint work
If you have the Azure Boards MCP Server connected to your AI agent in agent mode, you can use natural language prompts to identify and adjust work across your sprint.
| Task | Example prompt |
|---|---|
| Find overloaded members | Which team members are over capacity in Sprint 12 for <Contoso Team>? Show assigned work vs. capacity |
| Reassign tasks | Reassign task #5678 from <Jamal> to <me> in project <Contoso> |
| Move excess items to backlog | Move the lowest-priority user stories from Sprint 12 back to the backlog in <Contoso> |
| Check sprint balance | Show remaining capacity per team member for the current sprint in <Contoso Team> |
| Identify at-risk items | Which work items in Sprint 12 have remaining work greater than the days left in the sprint? |
| Suggest scope cuts | List the lowest-priority items in Sprint 12 that could be deferred to free up 16 hours of capacity |
| Split oversized stories | Find user stories in Sprint 12 with more than 20 hours of remaining task work and suggest how to split them |
| Compare planned vs. actual | Compare the original estimated hours vs. current remaining work for each team member in Sprint 12 |
| Redistribute after absence | <Raisa> is out for the rest of Sprint 12. Show her active tasks and suggest team members to reassign them to based on capacity |
| Mid-sprint health check | We're halfway through Sprint 12. Summarize completion percentage, remaining work, and flag any items with no progress |
Note
Agent mode and the MCP Server use natural language, so you can adjust these prompts or ask follow-up questions to refine the results.