Burndown and Velocity Charts
Agile project tracking visualizations that display work completion rates and team capacity, enabling data-driven sprint planning and progress monitoring in iterative development environments.
About this tool
Overview
Burndown and velocity charts are complementary Agile metrics that help teams track progress, estimate capacity, and improve sprint planning. While burndown charts show daily progress toward sprint completion, velocity charts measure team output over multiple sprints.
Burndown Charts
What They Show
A burndown chart displays the amount of work remaining in a sprint or release, typically measured in:
- Story points
- Ideal hours
- Tasks remaining
Key Elements
- X-Axis: Time (days in sprint)
- Y-Axis: Work remaining (story points or hours)
- Ideal Line: Straight diagonal showing perfect burndown rate
- Actual Line: Real progress, updated daily
Reading Burndown Charts
- Line above ideal: Team is behind schedule
- Line below ideal: Team is ahead of schedule
- Flat sections: No progress for that period
- Upward spikes: Scope increase (new work added)
Benefits
- Provides day-by-day measure of work completed
- Keeps team aware of scope creep
- Predicts likelihood of completing sprint work on time
- Promotes transparency and accountability
- Identifies blockers early
Velocity Charts
What They Measure
Velocity represents the amount of work (usually story points) a team completes in a single sprint. Tracking velocity over time helps teams:
- Estimate future sprint capacity
- Identify trends in productivity
- Plan releases more accurately
Calculation
Velocity = Sum of story points for all completed user stories in a sprint
Historical velocity is typically calculated as the average over the last 3-7 sprints.
Key Metrics
- Sprint Velocity: Work completed in individual sprint
- Average Velocity: Mean velocity over recent sprints
- Velocity Trend: Whether capacity is increasing, decreasing, or stable
Benefits
- Enables realistic sprint planning
- Improves long-term forecasting
- Identifies process improvements or degradation
- Helps predict release dates
- Supports commitment-based planning
How They Work Together
Complementary Insights
- Velocity: Focuses on team output over time (macro view)
- Burndown: Tracks daily progress within sprint (micro view)
Combined Usage
- Use velocity to determine sprint capacity during planning
- Use burndown to monitor daily progress during sprint
- Adjust velocity estimates based on burndown patterns
- Identify correlations between burndown patterns and final velocity
Best Practices
For Burndown Charts
- Update Daily: Track progress at the same time each day
- Don't Add Scope Mid-Sprint: Maintains chart integrity
- Investigate Anomalies: Flat lines or spikes indicate issues
- Focus on Trends: Don't overreact to single-day variations
For Velocity Tracking
- Use Consistent Estimation: Keep story point scale stable
- Track 5-7 Sprints: Provides reliable average
- Don't Game the System: Inflating velocity defeats the purpose
- Account for Team Changes: Adjust when team composition changes
- Consider External Factors: Holidays, training, incidents affect velocity
Common Pitfalls
Burndown Chart Issues
- The Hockey Stick: All work completed on last day (poor task breakdown)
- Stair Steps: Work updated infrequently instead of daily
- Scope Creep: Continuous upward movement from added work
Velocity Issues
- Velocity as Performance Metric: Using it to compare teams or judge individuals
- Constant Increase Expectation: Velocity should stabilize, not always increase
- Ignoring Context: Changes in team size, technology, or domain affect velocity
Tools
Most Agile project management tools include built-in charts:
- Jira (with Tempo Timesheets)
- Azure DevOps
- Rally
- VersionOne
- Targetprocess
- ZenHub
Advanced Variations
Burnup Charts
Show work completed (increasing line) instead of work remaining, making scope changes more visible.
Cumulative Flow Diagrams
Track work in different stages (To Do, In Progress, Done) over time, identifying bottlenecks.
Velocity Range Charts
Show velocity variability with error bars or bands to indicate expected range.
Metrics to Track Alongside
- Sprint commitment vs. completion rate
- Defect trends
- Cycle time and lead time
- Work in progress (WIP) limits
- Sprint retrospective action items
Loading more......
Information
Categories
Tags
Similar Products
6 result(s)Agile ceremony practice of brief daily team synchronization meetings, typically 15 minutes or less, focusing on progress updates, blockers, and daily plans to maintain alignment without excessive meeting overhead.
Agile metric measuring team output in story points per sprint, enabling predictable planning and continuous improvement through data-driven capacity assessment over multiple iterations.
Prioritization technique developed in 1994 for use in rapid application development and Agile methodologies. Categorizes requirements into Must have, Should have, Could have, and Won't have to reach common understanding with stakeholders on delivery priorities. Widely used with timeboxing in Scrum and DSDM.
Short 15-minute daily meeting in agile methodologies where team members synchronize work, discuss progress toward sprint goals, and identify blockers. Promotes collaboration, transparency, and quick problem resolution.
A relative estimation method in Agile that measures complexity, effort, and risk rather than time, using techniques like Planning Poker and tracking team velocity for predictable sprint planning.
A time-boxed period of 1-4 weeks in Agile project management during which a Scrum team works to complete predefined tasks and achieve specific goals, with most teams choosing 2-week durations.