Measuring Running Tested Features to drive agile software development practices

1. RTF M a metric for agility

2. discipline “ do, or do not … there is no try”

3. results goal oriented draws performance influences behaviour

4. priceless goal context : happiness metric : gifts received between pay days

5. sugar daddy goal context : happiness metric : gifts received between pay days

6. satisfaction goal context : customer service metric : available time

7. shit goal context : customer service metric : available time

8. effort goal context : software development metric : lines of code

9. nothing goal context : software development metric : lines of code

10. disaggregation lies damn lies statistics

11. RTF M running tested features metric

12. breakdown end user features automated acceptance tests integrated

13. burn up consistent features delivery from start to finish demands agility

14. waterfall big design up front delayed feature delivery bugs and rework

15. necessity 1 focus on feature delivery above design and architecture to grow feature count from the start

16. necessity 2 integrate early to grow feature count continuously

17. necessity 3 maintain customer contact to ensure features pass independent acceptance tests

18. necessity 4 automate tests to pass tests continuously

19. necessity 5 refactor to keep a clean design and maintain a smooth feature count growth curve

20. necessity 6 learn to be agile to deliver features in a continuous and improving stream

21. one metric to rule them all one metric to find them one metric to bring them all and in the darkness bind them