Save 37% off PRO during our Black Friday Sale! »

Tactics for Safely Using Agile Metrics in JIRA

Tactics for Safely Using Agile Metrics in JIRA

1100c19690e8eb006da7a35a6b17be97?s=128

Julia Wester

April 18, 2018
Tweet

Transcript

  1. Tactics for Safely Using Agile Metrics in JIRA @everydaykanban |

    @TeamLagom !1
  2. @everydaykanban | @TeamLagom !2 So many metrics… How do you

    choose?
  3. @everydaykanban | @TeamLagom !3 ship more value sooner start more

    or help finish lower WiP correlates to faster delivery Team’s current WiP levels Start with an outcome, not a metric Source: Larry Maccherone
  4. Don’t confuse activity with progress @everydaykanban | @TeamLagom !4 I

    sure do get a lot done! I add so much value! Activity metrics - lines of code - # of issues closed - # of deploys per day These aren’t “bad” metrics. We should: 1. Understand what they really show 2. Show them with competing metrics to reduce gaming
  5. Keep Your Metrics Balanced @everydaykanban | @TeamLagom !5 Quality How

    good is our work? Responsiveness How fast are we? Predictability How consistent are we? Predictability Do we meet commitments? Throughput Scrum-specific: Velocity # of Bugs created Cycle Time (Duration) Late vs. On-Time Issues Scrum-specific: Burndown / Burnup (multiple levels) Source: Larry Maccherone
  6. HOW @everydaykanban | @TeamLagom !6 HOW FAST? HOW CONSISTENT? MEETING

    COMMITMENTS? HOW GOOD?
  7. @everydaykanban | @TeamLagom HOW !7 HOW GOOD? Cumulative Flow Diagram

    filter on issuetype = Bug
  8. @everydaykanban | @TeamLagom !8 Reading a Cumulative Flow Diagram

  9. @everydaykanban | @TeamLagom HOW !9 HOW GOOD? Cumulative Flow Diagram

    filter on issuetype = Bug Blue band disappeared orange band is getting wider! orange band is getting narrower the purple band is completely horizontal
  10. @everydaykanban | @TeamLagom HOW !10 HOW FAST? Control Chart
 Filter

    by desired segment and date range Tip: Focus on trends over individual data points
  11. HOW MEETING COMMITMENTS? Release Burndown @everydaykanban | @TeamLagom !11 work

    completed = light green work remaining in version = light blue work forecast = grey DOES THIS MATCH EXPECTATIONS?
  12. @everydaykanban | @TeamLagom HOW MEETING COMMITMENTS? Sprint Burndown !12 You

    can use story points, issue counts or original time estimates The goal is to have the red line follow the gray line as much as possible! The red line should end up here at the end of the sprint
  13. @everydaykanban | @TeamLagom HOW !13 HOW CONSISTENT? Velocity Chart Is

    the amount we complete over time vary wildly or is it in the same “ballpark”? Essentially can I draw a narrow rectangle or must it be a wide rectangle?
  14. If your outcomes are team based, measure teams not individuals

    @everydaykanban | @TeamLagom !14
  15. For Advanced Flow Metrics and Probabilistic Forecasting… @everydaykanban | @TeamLagom

    !15
  16. @everydaykanban | @TeamLagom !16

  17. @everydaykanban | @TeamLagom !17