Using Reports to Plan Sprint or Iteration Schedules

This article explains how to use reports to plan for Sprints or Iteration schedules.

Overview

Before you create or define your sprint or iteration schedules, you must be able to determine the amount of work your team(s) can realistically handle over specific periods of time. Digital.ai Agility reporting provides historical perspective on team workloads, completion rates, and dependencies for past and current sprints and projects on which to base your new schedules.

Use History as a Guide

Use the team's prior velocity as a guide to determining how much to schedule within upcoming sprints. A consistent sprint length and team makeup provide for a reliable velocity that can be very effective in scheduling the future sprints. Use the Velocity Trend report to see historical velocity. Scroll back through the sprint schedule to view details of prior sprints. Schedule aberrations, such as large holiday periods, changing team sizes or a different sprint length should be discussed and taken into account during the sprint scheduling process.

Available Reports

The following reports are available in-line on Sprint or Iteration Planning to assist you in selecting a realize number of Backlog Items.

• Dependencies
• Portfolio Item Dependencies
• Velocity Trend

Some other reports you may consider reviewing as part of Sprint or Iteration Planning are:

• Workitem Trend
• Member Load Trend
• Project or Release Burndown
• Program Predictability
• Velocity By Date