+ All Categories
Home > Software > Agile metrics

Agile metrics

Date post: 12-Apr-2017
Category:
Upload: ankit-tandon
View: 138 times
Download: 0 times
Share this document with a friend
36
AGILE METRICS Measure the outcome, not output Webinar, 17 th April 2016 Presented By: Ankit Tandon https://in.linkedin.com/ in/ankit-tandon-04317631
Transcript
Page 1: Agile metrics

AGILE METRICS Measure the outcome, not output

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

Page 2: Agile metrics

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….

Page 3: Agile metrics

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

Page 4: Agile metrics

METRICS ARE NECESSARY FOR CONTINUAL IMPROVEMENT AND LEARNING

Page 5: Agile metrics

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

Page 6: Agile metrics

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

Page 7: Agile metrics

ONE SINGLE METRIC TO MEASURE EVERYTHING?

Page 8: Agile metrics

METRICS MYTHSVelocity measures outcome or value

Virat Kohli’s batting average while chasing is 59.14

Page 9: Agile metrics

METRICS MYTHS

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

Oops..

Page 10: Agile metrics

METRICS MYTHSHigher velocity is always a good thing

Risk of incurring technical debt

Page 11: Agile metrics

METRICS MYTHS Sprints Fail

There is no failure, only feedback

Page 12: Agile metrics

GOAL QUESTION METRICS- A FEW QUESTIONS TO PONDER

Goal Questions Metrics

Page 13: Agile metrics

GOAL QUESTION METRICS- A FEW QUESTIONS TO PONDER

Goal Questions Metrics

Page 14: Agile metrics

HOW SATISFIED IS OUR TEAM AND STAKEHOLDERS?

Happiness metric

1 2 3 4 5 6 7 8 9 100

0.51

1.52

2.53

3.54

4.55

Happiness

Sprint

Score

Page 15: Agile metrics

HOW SATISFIED IS OUR TEAM AND STAKEHOLDERS?

Net Promoter Score

1 2 3 4 5 6 7 8 9 100123456789

10

NPS

Release

Score

Page 16: Agile metrics

HOW SATISFIED IS OUR TEAM AND STAKEHOLDERS?

Customer Surveys and feedback

Page 17: Agile metrics

GOAL QUESTION METRICS- A FEW QUESTIONS TO PONDER

Goal Questions Metrics

Page 18: Agile metrics

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

Page 19: Agile metrics

GOAL QUESTION METRICS- A FEW QUESTIONS TO PONDER

Goal Questions Metrics

Page 20: Agile metrics

ARE WE INCREASING QUANTITY OF WORK BEING DELIVERED?

Throughput

1 2 3 4 5 6 7 8 9 100

1

2

3

4

5

6

Throughput

Sprint

Stories

Page 21: Agile metrics

ARE WE INCREASING QUANTITY OF WORK BEING DELIVERED

Release burndown

1 3 5 7 9 110

50

100

150

200

250

300

SP RemainingPlanned Trend

Sprint

Story point

Page 22: Agile metrics

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

Page 23: Agile metrics

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

Page 24: Agile metrics

GOAL QUESTION METRICS- A FEW QUESTIONS TO PONDER

Goal Questions Metrics

Page 25: Agile metrics

IS THE QUALITY UP TO THE MARK? Defect Leakage

1 2 3 4 5 6 7 8 9 1002468

101214

Defects

Sprints

Defects

Page 26: Agile metrics

IS THE QUALITY UP TO THE MARK? Code quality

There are many tools

to measure the code

quality like Sonar, PMD, Emma

etc

But the best way tofind it out is …

Page 27: Agile metrics

IS THE QUALITY UP TO THE MARK?

Automation Coverage

Page 28: Agile metrics

GOAL QUESTION METRICS- A FEW QUESTIONS TO PONDER

Goal Questions Metrics

Page 29: Agile metrics

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

Page 30: Agile metrics

ARE WE CONTINUOUSLY IMPROVING TEAM’S MATURITY?

Adhoc Work watcher

1 2 3 4 5 6 7 8 9 1002468

101214

Adhoc requ...

Sprints

Adhocworkrequest

Page 31: Agile metrics

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

Page 32: Agile metrics

ARE WE CONTINUOUSLY IMPROVING TEAM’S MATURITY?

Story spill over tracker

1 2 3 4 50123456

Spilled Stories

Release

Stories

Page 33: Agile metrics

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

Page 34: Agile metrics

-

Page 35: Agile metrics

-


Recommended