RTFM - A Metric For Agility
Upcoming SlideShare
Loading in...5
×
 

RTFM - A Metric For Agility

on

  • 1,284 views

Measuring Running Tested Features to drive agile software development practices

Measuring Running Tested Features to drive agile software development practices

Statistics

Views

Total Views
1,284
Views on SlideShare
1,283
Embed Views
1

Actions

Likes
1
Downloads
13
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

RTFM - A Metric For Agility RTFM - A Metric For Agility Presentation Transcript

  • RTF M a metric for agility
  • discipline “ do, or do not … there is no try”
  • results goal oriented draws performance influences behaviour
  • priceless goal context : happiness metric : gifts received between pay days
  • sugar daddy goal context : happiness metric : gifts received between pay days
  • satisfaction goal context : customer service metric : available time
  • shit goal context : customer service metric : available time
  • effort goal context : software development metric : lines of code
  • nothing goal context : software development metric : lines of code
  • disaggregation lies damn lies statistics
  • RTF M running tested features metric
  • breakdown end user features automated acceptance tests integrated
  • burn up consistent features delivery from start to finish demands agility
  • waterfall big design up front delayed feature delivery bugs and rework
  • necessity 1 focus on feature delivery above design and architecture to grow feature count from the start
  • necessity 2 integrate early to grow feature count continuously
  • necessity 3 maintain customer contact to ensure features pass independent acceptance tests
  • necessity 4 automate tests to pass tests continuously
  • necessity 5 refactor to keep a clean design and maintain a smooth feature count growth curve
  • necessity 6 learn 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