Key Takeaways

  • Burndown charts show remaining work over time, with the ideal line trending toward zero by Sprint end
  • Burnup charts show both total scope and completed work, making scope changes visible
  • Cumulative Flow Diagrams display work items in each status over time, revealing bottlenecks
  • Velocity tracking over multiple sprints provides the empirical basis for forecasting
  • Sprint Retrospectives enable continuous improvement through structured reflection
Last updated: January 2026

Agile Metrics & Tools

Agile metrics help teams understand their performance, identify problems early, and improve continuously. Unlike traditional metrics focused on cost variance, Agile metrics emphasize flow, value delivery, and team health.

Burndown Charts

A burndown chart tracks remaining work over time, showing whether the team is on track to complete their Sprint commitment.

Anatomy of a Burndown Chart

Story
Points    |*
Remaining | *
          |  *
  30      |   * <- Ideal Line (straight)
          |    *  *
  20      |     *   *
          |      *    * <- Actual (varies)
  10      |       *     *
          |        *      *
   0      +---+---+---+---+---+---
          D1  D2  D3  D4  D5  D6
                 Days
ElementDescription
Y-axisRemaining work (story points or tasks)
X-axisTime (days in sprint)
Ideal lineStraight diagonal from total to zero
Actual lineReal progress, updated daily

Reading a Burndown Chart

PatternInterpretation
Above ideal lineBehind schedule
Below ideal lineAhead of schedule
Flat sectionWork blocked or not progressing
Upward spikeScope added mid-sprint
Steep dropLarge item completed

Sprint Burndown Example

Day 1:  Start with 50 points
Day 2:  45 points remaining (5 completed)
Day 3:  42 points remaining (3 completed)
Day 4:  35 points remaining (7 completed)
Day 5:  30 points remaining (5 completed)
...continuing to Day 10: 0 points remaining

Updated daily during the Daily Scrum.


Burnup Charts

A burnup chart shows both total scope and completed work, making scope changes clearly visible.

Burnup Chart Structure

Story                            /------ Total Scope
Points   |              ------/
         |       ------/
  100    |------/
         |                    * * * * <- Completed Work
  75     |              * * *
         |        * * *
  50     |    * *
         |  *
  25     |*
         +---+---+---+---+---+---+---
           S1  S2  S3  S4  S5  S6  S7
                    Sprints
LineShows
Total scope lineAll work in the backlog
Completed work lineCumulative completed work
Gap between linesRemaining work

Burnup vs. Burndown

AspectBurndownBurnup
Shows scope changesHiddenClearly visible
Visual simplicitySimplerMore complex
Release planningSprint-focusedRelease-focused
Stakeholder communicationGood for sprintsBetter for releases

Cumulative Flow Diagram (CFD)

A Cumulative Flow Diagram displays the quantity of work items in each state over time, revealing bottlenecks and flow issues.

CFD Structure

Work
Items    |==================================== Done
         |=================================
  60     |==============================
         |=========================
  45     |==================== In Progress
         |==================
  30     |============
         |========
  15     |===== To Do
         |===
         +---+---+---+---+---+---+---+---
           W1  W2  W3  W4  W5  W6  W7  W8
                      Weeks

Reading a CFD

PatternIndicates
Parallel bandsSteady flow, healthy process
Widening bandWork piling up (bottleneck)
Narrowing bandWork clearing faster than arriving
Flat top lineNo new work entering system
Bulging middleWIP too high, items stuck

Key CFD Metrics

MetricMeaningMeasurement
Lead TimeTime from request to deliveryHorizontal distance across bands
WIPWork in progressVertical height of middle bands
ThroughputItems completed per time periodSlope of "Done" area

Velocity Tracking

Velocity is tracked over multiple sprints to establish a reliable forecasting baseline.

Velocity Trend Chart

SprintCommittedCompletedVariance
Sprint 13023-7
Sprint 22527+2
Sprint 32625-1
Sprint 42524-1
Sprint 52526+1

Average Velocity: 25 points/sprint

Velocity Guidelines

PracticeReason
Track 3+ sprintsNeed history for reliable forecasting
Use a rangePlan with low/average/high estimates
Don't compare teamsStory points are team-specific
Watch trendsConsistent is better than improving
Don't gamifyPressure to increase velocity corrupts data

Sprint Retrospective Tools

The Sprint Retrospective is where continuous improvement happens. Several techniques help structure the discussion:

Common Retrospective Formats

FormatStructure
Start-Stop-ContinueWhat should we start, stop, and continue doing?
Mad-Sad-GladWhat made us mad, sad, or glad this sprint?
4LsLiked, Learned, Lacked, Longed For
SailboatWind (helps), Anchors (slows), Rocks (risks), Island (goal)
TimelineWalk through sprint chronologically

Retrospective Best Practices

PracticeWhy
Safe environmentPeople must feel safe to be honest
Action itemsRetrospectives without actions are worthless
Follow throughTrack improvement items to completion
Rotate facilitationFresh perspectives keep it valuable
Time-box discussionsAvoid rabbit holes

Other Agile Metrics

Cycle Time and Lead Time

MetricDefinitionUse
Lead TimeRequest to delivery (customer perspective)Customer satisfaction
Cycle TimeWork start to work completion (team perspective)Process efficiency
ThroughputItems completed per time periodCapacity understanding

Quality Metrics

MetricWhat It Measures
Escaped DefectsBugs found after release
Test CoveragePercentage of code covered by tests
Technical DebtAccumulated shortcuts needing cleanup
Code ChurnHow much code is being rewritten

Team Health Metrics

MetricWhat It Indicates
Team HappinessMorale and engagement
Sprint Goal AchievementFocus and commitment
Retrospective Action CompletionImprovement follow-through
Sustainable PaceAre people burning out?

Using Metrics Effectively

Do's and Don'ts

DoDon't
Use metrics to improveUse metrics to punish
Track trends over timeObsess over single data points
Let teams own their metricsImpose metrics from above
Focus on outcomesFocus only on outputs
Measure what mattersMeasure everything possible

Metrics for Different Audiences

AudienceMetrics They Care About
DevelopersCycle time, code quality, technical debt
Product OwnerVelocity, release burnup, feature throughput
StakeholdersLead time, release dates, value delivered
ExecutivesBusiness outcomes, ROI, customer satisfaction

PMP Exam Tips

For PMP exam questions on Agile metrics:

  • Burndown charts show remaining work trending toward zero
  • Burnup charts reveal scope changes that burndowns hide
  • CFDs identify bottlenecks by showing widening bands
  • Velocity is for forecasting, not performance evaluation
  • Retrospectives drive continuous improvement

Key Takeaways

  • Burndown charts track remaining work toward Sprint completion
  • Burnup charts show scope changes and cumulative progress
  • Cumulative Flow Diagrams reveal bottlenecks and flow issues
  • Velocity should be tracked over 3+ sprints for reliability
  • Retrospectives turn insights into actionable improvements
  • Metrics should enable improvement, not punish teams
Loading diagram...
Agile Progress Tracking Tools
Test Your Knowledge

What does a flat section in a Sprint burndown chart typically indicate?

A
B
C
D
Test Your Knowledge

Which Agile chart best visualizes scope changes during a project?

A
B
C
D
Test Your Knowledge

In a Cumulative Flow Diagram, what does a widening band in the "In Progress" state indicate?

A
B
C
D