Velocity & Burndown Chart Patterns

Burndown charts are visual representations of work remaining over time in Agile project management. Recognizing different patterns in these charts helps teams identify potential risks, inefficiencies, or deviations from the planned progress.

Charles Darwin

Burndown charts

Default view

Ideal Pattern (Smooth Decline)

Text

1. The team is making steady, consistent progress.
2. Tasks were estimated accurately.
3. Work is being completed at a predictable pace.
4. No significant blockers or scope changes occurred
5. It never happends

Late Start Pattern

What is means

1. Team delayed starting work on sprint tasks
2. Initial tasks may have been blocked
3. Team might be procrastinating or has planning issues
4. Could indicate "student syndrome" - waiting until deadlines approach

Ways to overcome it

1. Break tasks into smaller ones - mini-deadlines
2. Set personal deadlines
3. Identify blockers
4. Start with easy tasks to build momentum
5. Hold yourself accountable

Scope Creep Pattern

What is means

1. New requirements or stories were added mid-sprint
2. Stories were underestimated in complexity
3. Poor sprint planning or changing priorities
4. May result in incomplete sprint with stories carrying over

Ways to overcome it

1. Better grooming
2. Better sprint planing
3. Better backlog prioritization

Early Completion Pattern

What is means

1. Team overestimated the work required
2. Team was more productive than expected
3. Some planned stories were simplified or removed
4. Team might not be challenging themselves enough

Ways to overcome it

1. Plan more effectively by refining estimations and adding valuable tasks

Struggling Team Pattern

What is means

1. Team underestimated complexity or effort
2. Technical challenges or blockers emerged
3. Team may be understaffed or facing skill gaps
4. Sprint planning may have been overly optimistic

Start - Stop Pattern

What is means

1. Team is context-switching between projects
2. Temporary blockers are halting progress
3. Team may be waiting for external dependencies
4. Bottlenecks in the workflow or uneven distribution of work

Velocity Chart

The What

A team's average sum of story points (or any other work units) completed per sprint

The what for

• Helps estimate the amount of work a team can complete in a sprint
• Makes sprint planning  realistic, creates predictability
• Less “gut feeling” - putting data into the process Shows team performance trends over time

Common Pitfalls

• Velocity !== Capacity (calendar days)
• Comparing velocity across teams
• Expecting velocity to increase constantly—it stabilizes over time
• Using velocity as a performance metric for individuals