1. how (fr)agile we are metrics in an Agile world Gaetano Mazzanti Gama-Tech

2. metrics goals & proxies !

3. goal #1 make money survive

4. deliver value to stakeholders make them successful/happy

5. success means different things to different people

6. proxy variables indirect measures

7. typical proxy variables efficiency schedule variance budget # of defects

8. measurement alters behavior

9. no process chaos agile traditional code & fix rigid process top-down orderedchaoticcomplex no metrics metrics for a linear, deterministic world which metrics?

10. product development is complex “self-organizing, non-linear, feedback systems are inherently unpredictable they are not controllable“ D.Meadows

11. however, we can watch, learn and work with the system

12. metrics learn & change

13. single loop learning resultsactions how efficiency doing things right incremental change lead to which shape future

14. double loop learning resultsactions values, assumptions why effectiveness doing the right things question assumptions radical change guide lead to new/improved efficiency doing things right incremental change how Chris Argyris

15. learn, change, move on resultsactions values, assumptions define metric* set expiration date result ok or expiration date passed? metric *shared, simple, controllable, transparent, time-bound

16. question assumptions command & control efficiency full capacity conform to plan reduce variability large batches large queues aligned self-organization focus on value optimize flow embrace change reduce waste small batches reduce queues Agile/Lean

17. metrics quadrants & queues

19. metrics quadrants* Lead Time Cycle Time Quality of Service (SLA) Throughput Business Value Lead Time Cycle Time Quality of Service (SLA) Throughput Business Value WIP Cadence CI Failures Rework Impediments Retrospectives Reviews Morale WIP Cadence CI Failures Rework Impediments Retrospectives Reviews Morale Revenues ROI Customer Satisfaction Revenues ROI Customer Satisfaction Code Quality Technical Debt Test Coverage Code Quality Technical Debt Test Coverage Team Maturity Business Product Process Bugs *thanks to Matteo Vaccari Paolo Perrotta Fabio Armani

20. metrics quadrants* Lead Time Cycle Time Quality of Service (SLA) Throughput Business Value Lead Time Cycle Time Quality of Service (SLA) Throughput Business Value WIP Cadence CI Failures Rework Impediments Retrospectives Reviews Morale WIP Cadence CI Failures Rework Impediments Retrospectives Reviews Morale Revenues ROI Customer Satisfaction Revenues ROI Customer Satisfaction Code Quality Technical Debt Test Coverage Code Quality Technical Debt Test Coverage Team Maturity Business Product Process Bugs *thanks to Matteo Vaccari Paolo Perrotta Fabio Armani what!? no velocity? what!? no velocity?

21. metrics quadrants Lead Time Cycle Time Quality of Service (SLA) Throughput Business Value Lead Time Cycle Time Quality of Service (SLA) Throughput Business Value WIP Cadence CI Failures Rework Impediments Retrospectives Reviews Morale WIP Cadence CI Failures Rework Impediments Retrospectives Reviews Morale Revenues ROI Customer Satisfaction Revenues ROI Customer Satisfaction Code Quality Technical Debt Test Coverage Code Quality Technical Debt Test Coverage Team Maturity Business Product Process Bugs fragile

22. metrics quadrants Lead Time Cycle Time Quality of Service (SLA) Throughput Business Value Lead Time Cycle Time Quality of Service (SLA) Throughput Business Value WIP Cadence CI Failures Rework Impediments Retrospectives Reviews Morale WIP Cadence CI Failures Rework Impediments Retrospectives Reviews Morale Revenues ROI Customer Satisfaction Revenues ROI Customer Satisfaction Code Quality Technical Debt Test Coverage Code Quality Technical Debt Test Coverage Team Maturity Business Product Process Bugs fragile agile

23. fragility code quality technical debt lack of advanced engineering practices (i.e. TDD, CI) => rework

24. code quality evolution a short video

25. backlogto do in progress done 2 2 agility

26. being agile is not the goal, it’s a mean if you are really interested there are plenty of agility tests on the Internet: Nokia Test Scrum Open Assessment - ScrumAlliance Agile Maturity Model Agile Evaluation Framework Comparative Agility Assessment etc.

27. impediments, retrospectives, reviews # of questions answered # of questions asked # action items addressed # action items assigned at previous meetings # of WTFs WTF!? ? ?

28. backlogs & taskboards everywhere tasks/user stories defects/SLA tickets impediments action items (reviews) new old kill old items! age based pruning

29. queues add cycle time risk variability overhead reduce quality motivation stop starting start finishing

30. cumulative flow diagram time in queue (cycle time) queue size (WIP) time cumulative quantity arrivals departures (throughput) source: Donald Reinertsen

31. cumulative flow diagram increasing queue size increasing cycle time time cumulative quantity WIP cycle time source: Donald Reinertsen

32. cumulative flow diagram WIP is a leading indicator time cumulative quantity WIP cycle time source: Donald Reinertsen

33. cumulative flow diagram large batches large queues time cumulative quantity

34. cumulative flow diagram small batches small queues time cumulative quantity source: Donald Reinertsen

35. cumulative flow diagram small batches continuous flow time cumulative quantity

36. Kanban board backlogto doin progressdone 22 cycle time cycle time = WIP throughput inspired by Henrik Kniberg

37. no WIP limit -> queue! 23 readybacklogto do in progress done

38. no WIP limit -> queue! 23 readybacklogto do in progress done flow = speed * density

39. Slack (%) optimize flow absorb variation

40. cumulative flow diagram WIP cycle time done in progress to do backlog time # user stories throughput

41. control charts source: Samuli Heljo

42. additional flow related metrics active WIP tasks that are really in progress and not waiting around (#,%,% of time spent) buffered WIP tasks waiting to be handed-off process efficiency active time / cycle time technical debt WIP / standard WIP # of projects a person works in parallel

43. Happiness Index MonTueWedThuFri Tom   Anne Paul  Joe  Eva  niko-niko calendar

44. how long since? you talked to a customer last useful retrospective you learned something at work your boss last freaked out last critical bug 52 days 6 weeks 2 days 3 1 week

45. and don’t forget bus factor # of key developers that need to be hit by a bus to kill a project

46. “per una vera mille sono finte” F. De André “for every true one thousands are fake”

48. Gaetano Mazzanti Gama-Tech @mgaewsj info@gama-tech.net