Define a sprint cadence for use by all teams within your product group. These Azure Boards tools rely on sprint assignments to a team Sprint backlogs, Taskboard, and Forecast and Delivery plans. You assign work to sprints that teams commit to deliver at the end of the sprint. Also, you can define sprints within a hierarchy that includes release trains. A sprint cadence can vary between one week to four weeks or longer. Sprints-specified by Iteration Paths-are defined for a project and then selected by teams. Add a team, move from one default team to several teams. Configure development teams to support rollup to project management feature teamsįor more information about configuring teams, see the following articles:. Define a team for each development group of six to 12 developers. Configure teams along the value streams your organization wants to deliver. This way, each team can work autonomously while collaborating with each other. However, if you have several development or feature teams, we recommend that you define a team in Azure DevOps for each feature team. Each project defines a default team, which you can start using immediately. Configure your teamsĪzure Boards provides each team a set of Agile tools to plan and track work. 
However, some of the features included in this article, such as Rollup, Analytics, and some portfolio planning tools, are only available for the cloud at this time.
Most of the guidance in this article is valid for both the cloud and on-premises versions. If your team is committed to practicing Kanban or Scrum methods, see instead About Boards and Kanban or the tutorials for implementing Scrum.
0 kommentar(er)
