Implement Scaled Agile Framework® in Azure Boards

Article
10/20/2021

TFS 2017 | TFS 2015 | TFS 2013

Many enterprises benefit from individual Agile teams. Greater interest grows to scale Agile practices as the organization grows. The need for enterprises to view progress of many Agile teams and across a portfolio continues to increase. To address these needs, many businesses have adopted the Scaled Agile Framework® (SAFe®).

If you're familiar with Scrum but not familiar with SAFe®, these videos at Scaled Agile are a good way to orient yourself.

Azure Boards supports SAFe® practices through its autonomous teams, backlogs, boards, reports, and metrics. This article introduces you to how Azure Boards artifacts support SAFe practices and artifacts.

The Scaled Agile Framework®
Essential SAFe®
Portfolio SAFe®
Large Solution SAFe®
Quick reference mapping
Azure Boards implementation of SAFe®

Note

This article is one of a set of Scaled Agile Framework® tutorials that applies to Azure Boards and Azure DevOps Services. Most of the guidance is valid for both the cloud and on-premises versions. However, some of the features and procedures are specific to the cloud or the latest version of Azure DevOps Server.

Scaled Agile Framework®

The SAFe® addresses how a portfolio vision is met by a hierarchy of teams, all concerned with specific goals. This framework breaks down Epics into Features and Stories. Teams work on these items in Sprints and deliver through Program Increments (PIs) and Release Trains. Furthermore, the portfolio backlog can track deliverables that map to value streams and associated budgets.

SAFe® architectural overview version 5.0

SAFe® and Scaled Agile Framework are registered trademarks of Scaled Agile Inc.

SAFe® 5.0 Business Agility

Many SAFe® practices include growing a culture that supports agility, alignment, and autonomy, all while being customer-centric.

Some of the ways Azure Boards supports business agility and agile culture are discussed in the following articles:

Essential SAFe®

Essential SAFe® requires support for the artifacts and practices illustrated in the following poster.

All of these artifacts and practices are supported by Azure Boards.

Stories, Features, and Enablers: Implemented as work items that capture information and status of work. These work items automatically appear on team backlogs and Kanban boards.
Team Backlogs and Program Backlogs: Implemented as team backlogs that filter work items assigned to a team and support prioritizing and grouping of work.
Scrum and Kanban: Practices that are fully supported using Kanban boards, Sprint backlogs and Taskboards, teams, and sprint cadences.
Iterations, Innovation and Planning (IP) Iteration, Program Increments (PI), Milestones, and Release Trains: Implemented via a flat-list or a hierarchical configuration of Iteration Paths.
Agile Release Train: Implemented by a set of Agile teams and Program teams configured to support specific team and program views.
PI Objectives, Team Goals, and Solution context: Teams can use the built-in project wiki to share objectives, goals, customer information, and solution requirements.

For an overview of how Azure Boards implements Scrum and Kanban, see About Sprints, Scrum, and project management and About Boards and Kanban.

Portfolio SAFe®

Portfolio SAFe® adds support for managing portfolios through epics, enablers, and value streams.

Azure Boards provides supports for the following portfolio components:

Epics: Map to the Epic work item type and allow tracking, grouping, and rollup of child items.
Portfolio backlogs: Implemented as a portfolio backlog that supports filtering of work based on review of business needs.
Portfolio Vision and Strategic Themes: Business owners and portfolio managers can use the built-in project wiki to share their vision, objectives, and goals.
Value Streams: Value streams can be tracked using tags or custom fields.
Lean budgets: Budget information can be captured in custom fields and rolled up to gain visibility to the Feature and Epic levels.
KPIs: Several reports and dashboard widgets provide out-of-the box metrics. Power BI and the Analytics service provide support to create custom reports quickly.

Large Solution SAFe®

Large Solutions SAFe® includes support for a Solution Backlog, Solution Trains, and Capabilities.

You can implement large solutions in much the same way as you implement Portfolio SAFe®. However, you can also add custom work item types and custom backlogs to support other solution requirements.

Full SAFe®

Full SAFe® includes the three levels of Essential SAFe®, Large Solution SAFe®, and Portfolio SAFe®.

How SAFe® artifacts map to Azure Boards

The following table maps SAFe® terms or artifacts to the equivalent Azure Boards term or artifact. Choose the link to learn about implementation details.

SAFe® term or artifact

Azure Boards term or artifact

Agile teams

Teams. You define a hierarchy of teams to meet the needs of feature or development teams, program and portfolio teams, or solution train teams.

Agile Release Train (ART)

Teams. Agile teams manage the work of deliverables for a set of Features. Each Agile team has a set of Agile tools to support the flow of work and review progress and deliverables.

Budgets

Tags, Value Area. You can use tags or the Value Area field to track work associated with a specific budget or value stream.

Capabilities

Work item. You define, plan, and track Capabilities similar to Epics and Features. You capture them in work items and within various team backlogs.

Enablers

Work item. You define, plan, and track Enablers similar to Epics, Features, and Stories. You capture them in work items and within various team backlogs.

Epics

Epic work item. You define an Epic using the Epic work item type. Epics are at the top of the work item hierarchy of Epics, Features, and Stories.

Features

Feature work item. You define a Feature using the Feature work item type. Features are a container for many Stories and are represented in their own portfolio backlog.

Innovation and Planning (IP) Iteration

Iteration Path. You define Iteration Paths for a project and set their start and end dates. Each team subscribes to the iterations they work with.

Iteration

Iteration Path. You define Iteration Paths for a project and set their start and end dates. Each team subscribes to the iterations they work with.

Milestones

Milestones and key events. Milestones occur at the end of each iteration. Custom fields and tags can also be used to associate work with milestones and key events.

Portfolio Backlog

Portfolio backlog. A portfolio backlog lists the Epics associated with a portfolio with the option to expand and display the child Features and Stories.

Portfolio Kanban

Portfolio Epics board. The Portfolio team's board displays the Epics backlog as cards in an interactive, configurable, and filterable Kanban board.

Portfolio Vision

Wiki. Use the project wiki to share broadly within the organization information related to strategy, solutions, and how teams will collaborate to produce portfolio and program deliverables.

Program Backlog

Feature backlog. A Feature backlog lists the Features associated with a program with the option to expand and display the child Stories.

Program Kanban

Program Features board. The Program board displays the Features backlog as cards in an interactive, configurable, and filterable Kanban board.

Program Increment (PI) Iteration Path

Iteration Path. Iteration Paths define a time box for a project with start and end dates. Iteration Paths can be defined from one week to 12 weeks or longer.

Retrospectives and reviews

Retrospectives. Each team can add a board to capture, prioritize, and create action items to support their improvement processes.

Roadmap

Delivery Plans, Feature Timeline. Azure Boards provides configurable and interactive views to review roadmaps and team deliverables.

Shared Services

Shared services team structure: Resources that are shared across teams can be represented through their own Agile feature team. Each can manage their backlog while having their work also appear in the backlogs of the teams they support.

Solutions

Solutions: Solutions can be represented through a custom Solution work item type.

Solution Backlog

Solution portfolio backlog. You can define a custom work item type and portfolio backlog to capture special business requirements of large solutions, or use Epics and Epic portfolio backlogs to capture solutions.

Strategic Themes

Wiki. Strategic Themes, similar to Portfolio Vision, can be captured in a project wiki.

Stories

User Story work item. User Stories capture the functionality you want to be delivered. They're typically sized so as to be completed with a single iteration.

Team Backlog

Stories backlog. The Stories backlog lists the User Stories assigned to the area path associated with the team.

Team Kanban

Stories board. The Stories board displays the Stories backlog as cards in an interactive, configurable, and filterable Kanban board.

Value Streams

Tags, Value Area. You can use tags or the Value Area field to track work associated with a specific budget or value stream.

Azure Boards implementation of SAFe®

Each of the following articles within this suite of tutorials provide details on how you can configure, customize, and use Azure Boards to implement your SAFe® programs and projects.

Try this next

How SAFe® concepts map to Azure Boards artifacts

Scale Agile to Large Teams
Agile culture
Practices that scale
About Sprints, Scrum and project management
About Boards and Kanban
Scaled Agile Framework: SAFe® resource site.
SAFe® in 7 minutes: video from Inbar Oren, the Lean Samurai.
Scaling Agile and SAFe® Metrics with TFS: Blog post that illustrates a SQL Server report developed by InCycle to illustrate how TFS can be used to support scaled agile or SAFe.

About the authors

Many thanks to the following contributors for their review and feedback to the current content.

Phillip Eng is a Senior Architect at Microsoft, Digital Pursuit and Guidance.
Hosam Kamel is a technology solution professional for Microsoft and ALM Ranger.
Willy-Peter Schaub is a former program manager with the Visual Studio ALM Rangers at the Microsoft Canada Development Center. You can follow Willy-Peter on Twitter at twitter.com/wpschaub.

The articles in this series were updated from a previous white paper developed in collaboration with the following authors:

Gordon Beeming is a Software Developer at Derivco in the sunny city of Durban, South Africa. He spends most his time hacking away at the keyboard in Visual Studio or with his family relaxing. His blog is at gordonbeeming.xyz and you can follow him on Twitter at twitter.com/gordonbeeming.
Brian Blackman is a principal consultant with Microsoft Premier Developer, focusing on affecting ISV partners and Enterprises success in engineering and the marketplace. He has an MBA, and is a CSM, CSP, MCSD (C++), and MCTS and is a Visual Studio ALM Ranger. When he's not Ruck Mastering and contributing to Visual Studio ALM Ranger projects, he spends his time writing code, creating and delivering workshops, and consulting in various concentrations, especially helping organizations in their quest for business agility.
Gregg Boer is a principal program manager at Microsoft. Gregg is the product owner for the Agile management experience provided by Azure DevOps and on-premises TFS.
Kathryn Elliott is a senior technical writer at Microsoft.
Susan Ferrell is a senior technical writer and a Visual Studio ALM Ranger.
Willy-Peter Schaub is a former program manager with the Visual Studio ALM Rangers at the Microsoft Canada Development Center. Since the mid-'80s, he has been striving for simplicity and maintainability in software engineering. You can follow him on Twitter at twitter.com/wpschaub.
Special thanks to the following technical experts for reviewing this article: Mike Douglas (independent consultant, ALM Ranger), Richard Hundhausen (independent consultant, ALM Ranger) and Bill Heys (independent consultant, ALM Ranger).

Partager via

Implement Scaled Agile Framework® in Azure Boards