Scrum and Kanban metrics


Sprint Burn down

Amount of work left in terms of stories/hours in the sprint – typically a forecast (ideal would be to complete all the forecasted work by end of sprint)

  • Possible issue that can be determined if the deviation is less or more than forecasted
    • Less: it means team has completed sprint early, which means team is not committing to enough work
    • More: if the team is not able to completed the sprint as per forecast by end of sprint, then they might committing too much work
      • Sprint scope may have been changed
      • Estimation was not right, possibility of breaking stories further

Epic and release burndown

Helps track the progress of development of overall project or larger work package. Sprint team might be stories from one or more epics, also different sprint team might have stories form same epics spread across.

  • Possible problem that can be determined if epics and release plan are not as per plan
    • Epic or release forecasts are not available to team and clarified by PO
    • No progress is been made over iterations by sprint teams, not shipping any output throughout the development cycle
    • Scope creep during sprints by product owner


Average amount of work the sprint team completes in the sprint, in terms of story points. Velocity will be considered as input to see how much time (iterations) the team takes to finish the backlog. Velocity should get better over the time, if there is dip in velocity should try to address with highest priority.

  • Possible issue if there is adverse trend in velocity
    • Impediments are not been addressed on time
    • Team is running beyond capacity
    • Estimation could be wrong, team overlooked/dint account for risk and dependencies



  • Visualize work flow
  • Limit WIP
  • Continuous measurement and improvement in life cycle

Lead time and cycle time

  • Lead time is the total amount of time spent a tasks takes to finish – starts when the new task is created and ends when the task is finished
  • Cycle time is the time actively taken/spend on the particular task – when the tasks is committed for working
    • Lead time > cycle time
    • Lead time = Done date – ready for development date
    • Cycle time = Done date – development start date
  • Cycle time can be improved with automation and process
  • Lead time can be improved by reducing idle time – this is what customer sees


  • Number of task finished per time unit
    • WIP / average lead time

CFD – cumulative flow diagram can be used to measure the average lead and cycle time. It’s a time based plot (mostly daily). X axis represents time frame and Y axis cumulative numbers of tasks and status over time.



  • bands are parallel – throughput is stable
  • band is rapidly narrowing – throughput is higher than entry(more capacity)
  • Band is rapidly widening – throughput is less, tasks entering Kanban board is more than leaving it
  • Kanban meeting – same as daily standup but blockers are discussed
  • Replenishment meeting – similar to product backlog, but not time boxed could be based on WIP
  • Service delivery review – similar to retrospective, but process improvement are discussed
  • Delivery planning meeting – ad hock, usually done few days before the release



Categories: Agile

Tags: , ,

%d bloggers like this: