Jag Gill2 July 2008

RTF Ma metric for agility

discipline“do, or do not …

there is no try”

resultsgoal oriented

draws performance

influences behaviour

pricelessgoal context : happiness

metric : gifts received between pay days

sugar daddygoal context : happiness

metric : gifts received between pay days

satisfactiongoal context : customer service

metric : available time

shitgoal context : customer service

metric : available time

effortgoal context : software

development

metric : lines of code

nothinggoal context : software

development

metric : lines of code

disaggregationlies

damn lies

statistics

RTF Mrunning

tested

features

metric

breakdownend user features

automated acceptance tests

integrated

burn upconsistent features delivery

from start to finish

demands agility

waterfallbig design up front

delayed feature delivery

bugs and rework

necessity 1focus on feature delivery above design and architecture to grow

feature count from the start

necessity 2integrate early to grow feature

count continuously

necessity 3maintain customer contact to

ensure features pass independent acceptance tests

necessity 4automate tests to pass tests

continuously

necessity 5refactor to keep a clean design and maintain a smooth feature

count growth curve

necessity 6learn to be agile to deliver

features in a continuous and improving stream

one metric to rule them all

one metric to find them

one metric to bring them all

and in the darkness bind them