Skip to content

Commit 1c3bc20

Browse files
Merge pull request #8283 from MicrosoftDocs/users/chcomley/refresh-plan-index
Refresh stale index.md boards/plans/index
2 parents 9a6ec81 + c182775 commit 1c3bc20

File tree

1 file changed

+132
-23
lines changed

1 file changed

+132
-23
lines changed

docs/boards/plans/index.md

Lines changed: 132 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,56 +1,165 @@
11
---
2-
title: Use Agile tools to use portfolios, dashboards, and delivery plans in Azure Boards
2+
title: Scale Agile practices with Azure Boards
33
titleSuffix: Azure Boards
4-
description: Learn how to scale Agile tools using portfolios, dashboards, and delivery plans in Azure Boards and Azure DevOps.
4+
description: Overview of Azure Boards scaling capabilities including portfolios, delivery plans, and dashboards for scaling Agile practices across teams.
55
ms.service: azure-devops-boards
66
ms.author: chcomley
77
author: chcomley
88
ms.topic: overview
99
monikerRange: '<= azure-devops'
10-
ms.date: 04/01/2022
10+
ms.date: 09/03/2025
1111
---
1212

13-
# Plan for Agile at scale
13+
# Scale Agile practices across teams
1414

1515
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1616

17-
As your organization grows, you want your tools to scale to support your growing business needs. Azure Boards tools scale primarily by supporting the addition of teams. Each team provides configurable tools that allow teams to focus on their set of work.
17+
As organizations grow, Azure Boards provides scalable tools to extend Agile practices across multiple teams and projects. The platform's team-based architecture enables both team autonomy and organizational visibility, supporting everything from small startups to large organizations.
1818

19-
> [!div class="mx-imgBorder"]
20-
> ![Agile tools and teams](../../organizations/settings/media/agile-tools/agile-tools-team-assets-post-2018.png)
19+
## Core scaling approach
2120

22-
For guidance on adding teams, see [About teams and Agile tools](../../organizations/settings/about-teams-and-settings.md).
21+
Azure Boards scales through a flexible team model where each team operates independently while contributing to larger organizational goals. This approach provides:
22+
23+
- **Team autonomy** with dedicated backlogs, boards, and sprint planning
24+
- **Organizational visibility** through portfolio rollups and cross-team reporting
25+
- **Flexible hierarchies** that adapt to your organizational structure
26+
- **Coordinated delivery** across multiple teams and projects
27+
28+
Each team gets their own configurable set of Agile tools while maintaining connections to the broader organizational context. For guidance on team setup, see [About teams and Agile tools](../../organizations/settings/about-teams-and-settings.md).
2329

2430
## Video: Agile at Scale
2531

2632
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=40ca5566-4875-4611-ba66-3ec22fa0c343]
2733
28-
## Portfolio management
34+
## Scaling capabilities
35+
36+
### Portfolio management
37+
38+
Portfolio management in Azure Boards enables executives and program managers to gain visibility across multiple teams and projects. Key capabilities include:
2939

30-
Enterprise project managers often have a portfolio of projects that they manage. These projects are typically developed by several teams. By creating a hierarchy of teams, portfolio managers can gain insight into the tools being developed by their teams.
40+
- **Multi-level work hierarchies** from epics down to tasks across teams
41+
- **Cross-team progress tracking** with rollup reporting
42+
- **Resource allocation visibility** and capacity planning
43+
- **Dependency management** between teams and projects
44+
- **Leadership dashboards** with high-level metrics and KPIs
45+
46+
Portfolio views help leaders understand delivery progress, identify bottlenecks, and make informed decisions about resource allocation and priorities.
3147

3248
For more information, see [Manage portfolios](portfolio-management.md).
3349

50+
### Delivery plans
51+
52+
Delivery Plans provide timeline-based coordination for multi-team environments. These interactive calendar views show:
3453

35-
## Delivery plans
54+
- **Cross-team feature delivery** across multiple sprints
55+
- **Timeline visualization** of planned work and milestones
56+
- **Dependency relationships** between teams and work items
57+
- **Capacity planning** and resource allocation insights
58+
- **Release coordination** for complex, multi-team deliveries
3659

37-
Delivery plans provide visibility into features under development by several teams across several sprints. With Delivery Plans, portfolio managers can review the schedule of stories or features their teams plan to deliver. Delivery Plans show the scheduled work items by sprint (iteration path) of selected teams against a calendar view.
60+
Delivery Plans help program managers coordinate releases, identify scheduling conflicts, and ensure aligned execution across development teams.
3861

3962
For more information, see [Review delivery plans](review-team-plans.md).
4063

41-
## Team dashboards
64+
### Multi-team dashboards
65+
66+
Azure Boards provides flexible dashboard capabilities for both operational and strategic reporting:
67+
68+
- **Team dashboards** for sprint tracking and daily operations
69+
- **Program dashboards** aggregating metrics across multiple teams
70+
- **Leadership dashboards** with strategic KPIs and health indicators
71+
- **Custom widgets** for organization-specific metrics
72+
- **Real-time data** reflecting current project status
73+
74+
You can tailor dashboards to different audiences, from developers tracking sprint progress to leaders monitoring overall portfolio health.
75+
76+
For more information, see [Add and manage dashboards](../../report/dashboards/dashboards.md?toc=/azure/devops/boards/plans/toc.json).
77+
78+
## When to use scaling features
79+
80+
### Portfolio management
81+
Use portfolio management when you need:
82+
- Visibility across multiple teams or projects
83+
- Leadership reporting on delivery progress
84+
- Cross-team dependency tracking
85+
- Resource allocation planning at scale
86+
87+
### Delivery plans
88+
Use delivery plans when you need:
89+
- Coordinated releases across multiple teams
90+
- Timeline visualization of feature delivery
91+
- Dependency management between teams
92+
- Capacity planning across sprints and teams
93+
94+
### Multi-team dashboards
95+
Use multi-team dashboards when you need:
96+
- Stakeholder reporting at various organizational levels
97+
- Real-time visibility into project health
98+
- Custom metrics specific to your organization
99+
- Automated reporting to reduce manual overhead
100+
101+
## Scaling considerations
102+
103+
When implementing Azure Boards at scale, consider these organizational, technical, and cultural factors that affect success.
104+
105+
### Organizational factors
106+
- **Team structure**: How teams are organized and their relationships
107+
- **Communication patterns**: How information flows between teams
108+
- **Decision-making processes**: Who makes what decisions and when
109+
- **Reporting needs**: What visibility different stakeholders require
110+
111+
For comprehensive guidance on scaling organizational practices, see [Practices that scale](practices-that-scale.md).
112+
113+
### Technical factors
114+
- **Work item hierarchies**: How work is broken down and organized
115+
- **Area path strategy**: How to organize work by feature or team boundaries
116+
- **Iteration alignment**: Whether teams share sprint schedules or operate independently
117+
- **Integration needs**: How Azure Boards connects with other development tools
118+
119+
To understand cross-team coordination approaches, see [Visibility across teams](visibility-across-teams.md).
120+
121+
### Cultural factors
122+
- **Agile maturity**: How comfortable teams are with Agile practices
123+
- **Collaboration patterns**: How teams work together and share information
124+
- **Change management**: How the organization adapts to new processes and tools
125+
- **Continuous improvement**: How teams and the organization learn and evolve
126+
127+
Learn more about fostering the right mindset in [Agile culture and scale](agile-culture.md). For broader organizational change, see [Agile culture](/devops/plan/adopting-agile).
128+
129+
## Benefits of scaling with Azure Boards
130+
131+
### For development teams
132+
- Maintain autonomy while contributing to organizational goals
133+
- Focus on their specific work without losing broader context
134+
- Collaborate effectively with other teams when needed
135+
- Access tools that adapt to their preferred working style
136+
137+
### For program managers
138+
- Gain visibility across multiple teams without micromanaging
139+
- Coordinate complex deliveries involving multiple teams
140+
- Identify and resolve cross-team dependencies
141+
- Plan and track progress toward larger organizational objectives
142+
143+
### For leadership
144+
- Understand delivery progress and organizational health
145+
- Make informed decisions about priorities and resource allocation
146+
- Track progress toward strategic objectives
147+
- Maintain visibility without detailed operational involvement
148+
149+
## Getting started with scaling features
150+
151+
Azure Boards scaling capabilities build upon foundational team practices. Organizations typically evolve their usage as they grow:
42152

43-
Each team can construct several dashboards to track and monitor their progress. Also, portfolio managers can create dashboards to monitor progress across several teams.
153+
1. **Start with individual teams** using basic backlogs and boards
154+
2. **Add cross-team visibility** as coordination needs emerge
155+
3. **Implement portfolio management** for leadership reporting
156+
4. **Scale delivery planning** for complex, multi-team releases
44157

45-
For more information, see [Add and manage dashboards](../../report/dashboards/dashboards.md?toc=/azure/devops/boards/plans/toc.json).
158+
The platform grows with your organization, supporting both simple team workflows and complex organizational scenarios.
46159

160+
Whether you're just beginning to scale or looking to optimize existing practices, these resources provide deeper insights into expanding team structures and optimizing dynamics:
47161

162+
- **Expand team structures**: Learn strategies to [scale Agile to large teams](/devops/plan/scaling-agile) effectively
163+
- **Optimize team dynamics**: Discover approaches for [creating productive teams](/devops/plan/building-productive-teams) at scale
48164

49-
## Related content
50-
51-
- [Visibility across teams](visibility-across-teams.md)
52-
- [Agile culture and scale](agile-culture.md)
53-
- [Practices that scale](practices-that-scale.md)
54-
- [Agile culture](/devops/plan/adopting-agile)
55-
- [Scale Agile to large teams](/devops/plan/scaling-agile)
56-
- [Creating productive teams](/devops/plan/building-productive-teams)
165+
These resources complement Azure Boards capabilities by addressing the people and process aspects of scaling Agile practices successfully.

0 commit comments

Comments
 (0)