CUTOUT AREA IN ZONE SPRINT LAYOUT HOW TO
CUTOUT AREA IN ZONE SPRINT LAYOUT UPDATE

Supports calendar views, cross-team views, and portfolio planning Developers might add them simply as a checklist of items they need to complete a user story or backlog requirement. If you don't plan on using these tools, then adding child-dependent tasks is optional. The Sprints tools support estimating and tracking remaining work and use of capacity planning. Many teams start out using Scrum methods to track and plan their work using the tools available through the Sprints hub.

Track dependencies across teams and projects: Dependency Tracker.

View progress bars, counts, or sums of rollup on tasks: Rollup.

Estimate work: Define Story Points, Effort, or Size.

CUTOUT AREA IN ZONE SPRINT LAYOUT UPDATE

Conduct daily scrums, update and monitor task status: Sprint Taskboard.

Monitor sprint burndown based on remaining work such as hours or days: Sprint burndown.

Track estimated and remaining work: Taskboard.

Plan and track capacity: Sprint capacity tool.

Forecast sprints using team velocity: Forecast.

Quickly define and prioritize backlog items: Product backlog.

Recommended for teams that follow Scrum methods and want to track time associated with work. Backlog work item types correspond to the Requirements category. The default work item types for each supported process are shown in the following tabs. This hierarchy supports a product backlog and portfolio backlog(s). Each process-Agile, Basic, Scrum, and CMMI-supports a set hierarchy of work item types.

For a comparison of each process, see Choose a process. The first choice made in work tracking is the process selected when creating a project. Once you determine how you'll use the work tracking building blocks and tools, you'll want to make any necessary configurations and customizations to support your business and communicate to your teams how they should use the tools. How you'll inform upper management of progress, status, and risks.How you'll use portfolio backlog levels.Whether or not you'll use tasks to track time and capacity.Whether you'll track bugs as requirements or as tasks, or not use bugs at all.How you'll use your product backlog to plan and prioritize your work.Work item type customizations or custom work item types.

CUTOUT AREA IN ZONE SPRINT LAYOUT HOW TO

How to structure area paths to support portfolio management views.

The primary items to consider as you structure your project are: Whether your teams follow Scrum, Kanban, or some combination of Scrumban, you can gain the most advantage of the Azure Boards tools by understanding the dependencies they have on configurations and customizations. When configuring or customizing work tracking tools, you'll want to consider the tools your teams use and how they will use them. If you're just getting started as a Project Administrator, see also Get started as an administrator.

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 is valid for both the cloud and on-premises versions. This article applies to Azure DevOps Services.

Cutout area in zone sprint layout