Webinar on Agile Metrics

© 2014 iZenBridge | CONFIDENTIAL

Webinar

on

Agile Metrics

By Saket Bansal


About Me…


Agenda

About Metrics

Common Agile Metrics

The Economic View


When a Measure becomes a target, it ceases

to be a good measure

Goodhart's Law

Warning


Metric

A metric is a standard for measuring or

evaluating something.


Measurement Dimensions

• Productivity

• Time to Market

• Predictability (Release / Sprint)

• Quality (Code base / Technical

Debts )

• Customer Satisfaction

• Employee Satisfaction

• Deviations / Variances

• Profitability


Good Use

• Used in retrospectives to

creates shared perspective

and diagnosis

• Feedback to correct planning

• Feedback for Prioritization

• Maintaining healthy code

base


Bad Use

• Evaluating Team

• Evaluating Individual

• Giving Target

• Showing progress


Agile Metrics


Velocity

• Expressed as the

number of story points

(or ideal days)

completed.

• Only stories or features

that are complete

counted

• Is an empirical

observation

• Helps us in refining the

release plan.

15

17

15

18 19

12

20 20

20

15

10

5

Sprints V

elo

cit

y

Velocity / Capacity Ratio (in

Person Days)


Stories Started But Not Done

• Sum up all the story

points that the team

started but could not done

• Should trend toward zero

• Measure of wasted work

5

10

2 2

5

20

15

10

5

Sprints

Sto

ry

Poin

ts


140

120

100

80

60

40

20

0

Technical Debt Incurred This Sprint

2

7

12

20

15

10

5

Sprints

Tech

nic

al D

ebt

in S

tory

Poin

ts


Sprint Burndown Chart (Hrs Or Story Points)

Days

Ideal H

ou

rs

55

38

20

10

Days

Sto

ry P

oin

ts


Release Burndown Chart

Iterations

Poin

ts

250

200

150

100

50

0

1 2 3 4 5 6 7 8

Planned

Actual


Sprint Goals

100

75

50

25

Sprints

% G

oal com

ple

tion

Fail

Sprints

Pass /

Fail

Pass


Self Assessment Metrics

0%

20%

40%

60%

80%

100%

Technical Excellence


Value Point Delivered

• Value points give per story by

Content Owner

• Value points of only done

stories counted

• Helps in priority alignment

15

17

15

18 19

12

20 20

20

15

10

5

Sprints

Valu

e P

oin

ts


Defects (In Story Points)

• Sum of defects (in story

points) from defect backlog

• Shows amount of work

getting added because of

defects

• Should be near to zero

140

120

100

80

60

40

20

0


http://iZenBridge.com/

http://scaledagileframework.com/


The Economic View


Beyond Proxy Variables

• Should we delay the release by

one month to fix the defects ?

• Should we reduce the cycle time

by adding one more team?

• Should we delay the release to

add functionality?

• Should we delay the project by

one month to get more

innovative ?


The Economic View

Value

added

Risk

Cycle Time

/ Delays

Product

Life Cycle

Profit


Sample Economic Framework

0

200

400

600

800

1000

1200

1 2 3 4

Product Life Cycle Profit

Life Cycle

Profit

Product

Value

Development

Expense

EMV of

Risks

Cost of

Delay = - - -


References

• http://agileatlas.org/articles/item/metrics-for-a-scrum-team

• The Principles of Product Development Flow , Donald G.

Reinertsen

http://agileatlas.org/articles/item/metrics-for-a-scrum-team












Our Training Offering

• Online Training

• PMP

• PMI-ACP

• PMI-PBA

• Classroom Training (Delhi /

Hyderabad / Pune / Mumbai /

Bangalore )

• SAFe Agilist

• PMI-ACP

• CSD (Certified Scrum

Developer)

• PMP

• PMI-PBA


Stay Connected

YouTube

www.youtube.com/izenbridge

www.iZenBridge.com

forum.iZenBridge.com

http://www.izenbridge.com/


http://iZenBridge.com/

PDUs / SEUs ?

http://scaledagileframework.com/

Engineering

Webinar on Agile Metrics