Agile metrics

transcript

AGILE METRICS Measure the outcome, not output

Webinar, 17th April 2016Presented By: Ankit Tandonhttps://in.linkedin.com/in/ankit-tandon-04317631

WHAT IS A METRIC

A metric is a measure for quantitatively assessing, controlling or selecting a person, process, event, or institution, along with the procedures to carry out measurements and the procedures for the interpretation of the assessment in the light of previous or comparable assessments.

-Wikipedia

Too much information….

WHAT IS A METRIC- LETS KEEP IT SIMPLE It measures and radiates information

METRICS ARE NECESSARY FOR CONTINUAL IMPROVEMENT AND LEARNING

WHY METRICS ARE IMPORTANT IN SOFTWARE DEVELOPMENT Because while executing projects,

TYPE OF METRICS Business metrics – RTF (Running Tested Features) – Earned Business Value (EBV) –

Net Present Value (NPV) – Internal Rate of Return (IRR) – Return of Investment (ROI) Code Metrics – Cyclomatic complexity – Best practices violation – Coding standards

violation – Possible bugs – Code duplication – Code coverage – Dead code – Test Quality

Design Metrics – –Code dependencies Incoming (Afferent Coupling) Outgoing (Efferent Coupling)

– Abstractness Do we really need all of these..? Number of abstract classes and interfaces Number of concrete classes Process metrics – Agile practice maturity – Impediments cleared per iteration –

Impediments carried over the next iteration – User stories carried over the next iteration – User stories done per iteration – Defects carried over the next iteration – Defects carried over the next iteration – Team member loading – Velocity of development – Backlog size

Automation Metrics – Code coverage – Number of builds per day – Time taken per build – Number of failed/success builds – Trends in code metrics

Testing Metrics – Acceptance tests per story – Defects count per story – Test time to run – Tests run frequency – Manual tests per story – Automation percent – Time to fix tests

ONE SINGLE METRIC TO MEASURE EVERYTHING?

METRICS MYTHSVelocity measures outcome or value

Virat Kohli’s batting average while chasing is 59.14

METRICS MYTHS

So for sure he is going to score that many today…

Oops..

METRICS MYTHSHigher velocity is always a good thing

Risk of incurring technical debt

METRICS MYTHS Sprints Fail

There is no failure, only feedback

GOAL QUESTION METRICS- A FEW QUESTIONS TO PONDER

Goal Questions Metrics

HOW SATISFIED IS OUR TEAM AND STAKEHOLDERS?

Happiness metric

1 2 3 4 5 6 7 8 9 100

Happiness

Sprint

Net Promoter Score

1 2 3 4 5 6 7 8 9 100123456789

Release

Customer Surveys and feedback

IS DEVELOPMENT EFFORT ALIGNED WITH BUSINESS?

Velocity vs Business value earned

1 2 3 4 5 6 7 8 9 1005

1015202530354045

VelocityBV

Sprint

Points

ARE WE INCREASING QUANTITY OF WORK BEING DELIVERED?

Throughput

1 2 3 4 5 6 7 8 9 100

Throughput

Sprint

Stories

ARE WE INCREASING QUANTITY OF WORK BEING DELIVERED

Release burndown

1 3 5 7 9 110

SP RemainingPlanned Trend

Sprint

Story point

ARE WE INCREASING QUANTITY OF WORK BEING DELIVERED?

Release burnup

1 2 3 4 5 6 7 8 9 100

50100150200250300

TotalCompleted

Sprint

Story point

ARE WE INCREASING QUANTITY OF WORK BEING DELIVERED? Forecasted vs Actual Velocity

1 2 3 4 5 6 7 8 9 1005

101520253035404550

Forecasted Ve-locityActual Velocity

Sprints

Story points

IS THE QUALITY UP TO THE MARK? Defect Leakage

1 2 3 4 5 6 7 8 9 1002468

101214

Defects

Sprints

Defects

IS THE QUALITY UP TO THE MARK? Code quality

There are many tools

to measure the code

quality like Sonar, PMD, Emma

But the best way tofind it out is …

IS THE QUALITY UP TO THE MARK?

Automation Coverage

ARE WE CONTINUOUSLY IMPROVING TEAM’S MATURITY?

Limiting WIP

Put a new dot each day for tasks In Progress

Calculate the dots and use it as an input for retrospective

Adhoc Work watcher

1 2 3 4 5 6 7 8 9 1002468

101214

Adhoc requ...

Sprints

Adhocworkrequest

ARE WE CONTINUOUSLY IMPROVING TEAM’S MATURITY? Cycle Time Average Time to complete

Should be as less as possible

Matured Agile teams and organizations should observe low cycle time

Story spill over tracker

1 2 3 4 50123456

Spilled Stories

Release

Stories

SUMMARY Good Agile Metrics:-

Affirm and Re-inforce desired behavior

Measure outcome not output

Easy to collect

Reveal context. Measure trends not numbers.

Fuel more discussions

Amplify learning

Vital few

REFERENCES -

http://www.scrum.nl/media/Agile_Metrics/$FILE/whitepaper_agile_metrics.pdf

http://sugsa.org.za/uploads/2009/09/measuring-for-results-2-small.pdf

http://www.slideshare.net/sergekovaleff/agile-base-camp-agile-metrics?qid=0d870c6f-86dc-4c88-b4a8-9145ef7fa607&v=&b=&from_search=11

Agile metrics

Software