![Agile Metrics That Matter Patricia (Patty) Carlin General Manager, ThoughtWorks Bangalore [email_address] www.thoughtworks.com www.studios.thoughtworks.com](https://image.slidesharecdn.com/agilemetricsthatmatterupload-100222045830-phpapp01/85/Agile-Metrics-That-Matter-2-320.jpg)
Uploaded byThoughtWorks Studios
Agile Metrics That Matter
This webinar covered important agile metrics for software development projects and how to measure the right things. It discussed what makes a good metric, focusing on metrics that can be acted on and measured at the appropriate level. The webinar also addressed which stakeholders want what information and factors that influence metric choice, such as the agile process used. Finally, it provided examples of common agile metrics like velocity, defects, and cycle time, and characteristics of good agile metrics.
More Related Content
![Confidentiality ppt[1] (1)](https://cdn.slidesharecdn.com/ss_thumbnails/confidentialityppt11-160811082409-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Agile Metrics That Matter
Agile Metrics That Matter
- 1. Welcome to theAgile Webinar on Agile Metrics that Matter The webinar will begin at 11 am GMT/ 4.30 pm IST NOTE: : Please adjust the volume of your headphone/speakers to hear the speaker clearly.
- 2. Agile Metrics That Matter Patricia (Patty) Carlin General Manager, ThoughtWorks Bangalore [email_address] www.thoughtworks.com www.studios.thoughtworks.com
- 3. What information shouldbe measured and tracked for Agile software development projects? Which metrics are useful and which are just useless busywork? How are different kinds of metrics used and how can they be misused? What happens when we measure the wrong things? Which stakeholders are interested in which sorts of information? What we’ll cover today
- 4.
- 5.
- 6.
- 7.
- 8. Everything that canbe counted does not necessarily count; everything that counts cannot necessarily be counted. -- Einstein
- 9. Tell me howyou will measure me and I will tell you how I will behave -- Goldratt
- 10. Measures something onlyif you plan to act on the results Measures only what can be measured Measures at the correct level and in the correct units Is easy to collect What makes a Metric “good”?
- 11. Guiding Agile PrinciplesOur highest priority is to satisfy the customer through early delivery of valuable software Working software is the primary measure of progress
- 12. What do yourStakeholders want? All the information they need to make decisions, and no more Information at the level of detail they can use Information at the scope they care about Information pertaining to the time frame they care about
- 13. Other factors thatinfluence your choice of metrics ... General style of the Agile process Type of work being done
- 14. Metrics Checklist NameQuestion being Answered Basis of Measurement Level & Usage Expected Trend When to Use It When to Stop Using It How to Game It Warnings
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23. Affirm and reinforcelean / agile practices Measure results, not output Follow trends not numbers Belong to a small set of metrics / diagnostics Provide fuel for meaningful conversation Diagnose & improve the processes that produce business value Provide feedback on a frequent and regular basis Are easy to collect Good Agile Metrics
- 24. Keep in mindthat change is difficult and that new metrics may be resisted if their message is problematic or unsettling.
- 25.
- 26. Thank you forattending the Agile webinar on Agile Metrics that Matter