Skip to main content

Project or Release Reports

Project or release reports provide comprehensive metrics to measure progress as teams execute work. These reports help program managers, release train engineers, and leadership track delivery against plans and make data-driven decisions.

Report Categories​

Project and release reports fall into several key categories:

Progress and Burndown Reports​

Track work completion and remaining effort over time:

Velocity and Capacity Reports​

Measure team output and plan future work:

Dependency Reports​

Identify and manage cross-team and cross-project dependencies:

Scope and Change Reports​

Monitor scope changes and their impact:

Predictability Reports​

Assess team and program commitment accuracy:

Quality and Cycle Time Reports​

Understand work quality and flow efficiency:

Choosing the Right Report​

Report TypeBest ForPrimary UsersFrequency
BurndownRelease tracking, sprint progressScrum Masters, Team LeadsDaily/Weekly
VelocityForecasting, capacity planningProduct Owners, PlannersSprint/Release review
Cumulative FlowIdentifying bottlenecks, WIP limitsKanban teams, Process improvementWeekly
DependenciesRisk management, coordinationProgram managers, RTEsPI planning, weekly
Scope ChangeChange management, trend analysisRelease managers, ProductWeekly/Monthly
PredictabilityCommitment accuracy, PI healthRTEs, LeadershipEnd of PI
Cycle TimeProcess improvement, efficiencyTeams, CoachesSprint retrospectives

Common Use Cases​

Release Planning​

  1. Review historical velocity to forecast release capacity
  2. Identify dependencies that could impact delivery
  3. Set realistic scope based on team capacity
  4. Track scope changes throughout release

PI Planning​

  1. Use velocity reports to set PI objectives
  2. Review dependency list reports to identify cross-team coordination needs
  3. Establish program predictability baseline
  4. Plan capacity considering team availability

Release Tracking​

  1. Monitor burndown to identify risks early
  2. Review cumulative flow to ensure healthy work distribution
  3. Track scope changes and their impact
  4. Check cycle time to identify process issues

Retrospectives and Improvement​

  1. Analyze velocity trends to evaluate process changes
  2. Review cycle time to identify improvement opportunities
  3. Examine cumulative flow patterns for bottlenecks
  4. Use predictability data to improve estimation

Stakeholder Communication​

  1. Use burndown reports in status meetings
  2. Share velocity trends to set expectations
  3. Communicate scope changes with rationale
  4. Report on program predictability in PI reviews

Best Practices​

Report Review Cadence​

Daily

  • Burndown reports during standups
  • Cumulative flow for Kanban teams

Weekly

  • Velocity trend monitoring
  • Dependency status reviews
  • Scope change tracking

Sprint/Iteration

  • Comprehensive velocity analysis
  • Cycle time review
  • Retrospective data analysis

PI/Release

  • Program predictability assessment
  • Long-term velocity trends
  • Release scope analysis

Data Quality​

  1. Ensure accurate estimates: Reports depend on quality estimation
  2. Update status regularly: Cumulative flow requires current status data
  3. Close completed work: Burndown accuracy depends on timely closures
  4. Maintain dependencies: Keep dependency data up-to-date
  5. Track scope changes: Document reasons for additions/removals

Cross-Report Analysis​

Don't rely on single reports in isolation:

  • Burndown + Velocity: Understand if burndown issues are capacity or scope problems
  • Cumulative Flow + Cycle Time: Identify specific bottlenecks causing delays
  • Dependencies + Predictability: See how dependencies impact commitments
  • Scope Change + Velocity: Understand impact of changes on team output

Avoiding Pitfalls​

Don't:

  • Use velocity to compare different teams
  • Ignore context when interpreting trends
  • Focus only on output metrics without quality measures
  • Make decisions based on single sprint data points
  • Pressure teams to increase velocity artificially

Do:

  • Track trends over multiple sprints
  • Consider external factors affecting metrics
  • Balance output with outcome measures
  • Review patterns across 3-5 sprints minimum
  • Use data to identify improvement opportunities

Prerequisites​

  • Effort Tracking: Many reports require effort tracking to be enabled
  • Estimation: Velocity and capacity reports need estimated work items
  • Status Workflow: Cumulative flow requires defined status categories
  • Dependencies: Dependency reports need dependency relationships created
  • Date Tracking: Burndown and trend reports need accurate start/end dates

Technical Considerations​

Report Performance​

  • Large data sets may take longer to generate
  • Use filters to focus on relevant timeframes
  • Export large reports for offline analysis

Data Refresh​

  • Most reports show real-time or near-real-time data
  • Historical data may require time for aggregation
  • Trend reports need multiple data points (minimum 2)

Filtering​

All project/release reports support filtering by:

  • Project or program context
  • Team assignments
  • Date ranges
  • Sprint or iteration
  • Work item types