Implement Scaled Agile Framework® in Azure Boards

 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 board.

Portfolio Vision

Wiki. Use the project wiki to share broadly within the organization information related to strategy, solutions, and how teams 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 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 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.

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources and services.
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed without them. If these are not fulfilled, the project is con
Read more

Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing  container-based workload is Kubernetes . Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse. At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling. Finally,
Read more