1. Scrum Metrics for Hyper-Productive Teams: How They Fly like Fighter Aircraft By Jeff Sutherland and Scott Downey
2. Scrum Metrics for Hyper-Productive Teams: How They Fly like Fighter Aircraft By Jeff Sutherland and Scott Downey
3. What’s Ahead Goal Tuning the Scrum Meetings Metrics: Math and Purpose The RoboScrum Workbook
4. What’s Ahead Goal Tuning the Scrum Meetings Metrics: Math and Purpose The RoboScrum Workbook
5. Jeff Sutherland Chairman, Scrum Training Institute CEO Scrum, Inc. & Sr. Advisor toOpenView Venture Partners Agile Coach for OpenView Venture Partners portfolio companies CEO/CTO/VPE for 11 Software Companies Created first Scrum at Easel Corp. in 1993 Rolled out Scrum in the next 7 Companies Achieved Hyper-Productive State in All Companies. Signatory of the Agile Manifesto Founder of the Agile Alliance http://www.JeffSutherland.com Jeff@ScrumInc.com
6. Jeff Sutherland Chairman, Scrum Training Institute CEO Scrum, Inc. & Sr. Advisor toOpenView Venture Partners Agile Coach for OpenView Venture Partners portfolio companies CEO/CTO/VPE for 11 Software Companies Created first Scrum at Easel Corp. in 1993 Rolled out Scrum in the next 7 Companies Achieved Hyper-Productive State in All Companies. Signatory of the Agile Manifesto Founder of the Agile Alliance http://www.JeffSutherland.com Jeff@ScrumInc.com
7. Scott Downey Head Agile Coach, Napster Formerly Head Agile Coach, MySpace 68 Delivery Teams Created Immersive Scrum Training System for Rapid Bootstrapping of Hyper-Productive Teams Average Improvement was over 600% Average Boot-Up took only 4.5 Weeks Co-Teaching CSM with Jeff since 2007 Shock Therapy: A Bootstrap for Hyper-Productive Scrumat Agile ‘09 with Jeff and Björn Granvik http://www.RapidScrum.com Scott@RapidScrum.com
8. Scott Downey Head Agile Coach, Napster Formerly Head Agile Coach, MySpace MySpace had 68 Delivery Teams Created Immersive Scrum Training System for Rapid Bootstrapping of Hyper-Productive Teams Average Improvement was over 600% Average Boot-Up took only 4.5 Weeks Co-Teaching CSM with Jeff since 2007 Shock Therapy: A Bootstrap for Hyper-Productive Scrumat Agile ‘09 with Jeff and BjörnGranvik http://www.RapidScrum.com Scott@RapidScrum.com
9. Goal To develop and standardize a set of Minimally-InvasiveMetrics that will help Scrum Masters Evaluate and AdviseTeams while providing Rich Insights about Team performance and a Fully PortableLanguage for team comparison across an Enterprise.
10. INVEST Mnemonic Refresher I mmediately Actionable N egotiable V aluable E stimable S ized to Fit T estable Thanks to Bill Wake for the acronym. See www.xp123.com.
11. Tuning the Scrum Meetings Creating a Culture of Hyper-Productivity
12. Tuning the Scrum Meetings Creating a Culture of Hyper-Productivity
13. Tuning the Scrum Meetings Sprint Planning Meetings Anchoring the Scale A New Perspective on INVEST Value, Voice and Visibility Daily Stand-Up Meetings The Fourth Question
37. The Fourth Question What did WE Achieve Yesterday on Priority 1? What did you Achieve Yesterday on Priority 1? What will you Achieve Today on Priority 1? Is anything blocking or jeopardizing your progress on Priority 1? Information Radiator What will WEAchieve Today on Priority 1? Is anything blocking or jeopardizing OURprogress on Priority 1? What will WEAchieve Today on Priority 1? Is anything blocking or jeopardizing OURprogress on Priority 1? Compared to our Keystone, how many Story Points did WE Achieve yesterday on Priority 1? SPO 3 SM
45. Metrics: Velocity Original Estimate: 8 Story Points 3 SPO 8 Estimate Priority 2 5 Original Estimate: 3 Story Points Priority 3 3 Velocity = 8 Priority 1 Original Estimate: 5 Story Points 5 11
46.
47. …need… a way to measure how much work the Team can do in a given Sprint, whether it results in an Approved Card or not,
48. …so that… I can quantify the Team’s entire capability, ask intelligent questions about distractions and take action to optimize the conversion of Effort into Value.
50. Metrics: Work Capacity 3 2 1 5 8 13 3 Priority 2 5 Priority 3 What have we achieved today on Priority 1? Item 1 Item 2 8 Priority 1
51. Metrics: Work Capacity 3 3 SPO Original Estimate: 8 Story Points 8 Estimate Priority 2 Priority 2 8 Work Reported : 8 Story Points Reported Work Capacity= 5 5 Priority 3 Priority 3 Velocity= Original Estimate: 3 Story Points 3 Work Reported: 2 Story Points 2 8 Priority 1 Original Estimate: 5 Story Points 5 Work Reported : 7 Story Points 7 11 17
57. Metrics: Focus Factor Attempts to force non-deterministic systems to operate at greater than 80% efficiency will cause short bursts of stabilization followed by extreme periods of destructive and unpredictable variations from that goal. 64.7% Work Capacity Velocity 11 17 W. Edwards Deming
60. …need… a metric that clearly shows if the Team has a tendency to under Commit and is consistently having to pull work forward from the Product Backlog before the end of the Sprint
61. …so that… I can encourage the Team toward higher Commitments during the Sprint Planning Meetings without the risk of pushing them to failure.
63. Metrics: Adopted Work Original Commitment: 0 3 4 9 11 19 19 PBL SBL In Prog DONE Adopted Work: 0 0 0 0 0 0 13 3 Total Commitment: 0 3 4 9 11 19 32 1 5 Adopted Work = 13 ÷ 19 = 68.4% INVEST 2 8 13 5 Sprint-O-Meter 8 Day 3 Day 2 3 Day 4 Day 5 Day 1 5
64. Metrics: Adopted Work Sprint-O-Meter Day 3 Day 2 Day 4 Day 5 Day 1
65.
66. …need… a clear way to measure the likelihood of unexpected work based on a Card’s Original Estimate
67. …so that… I can offer advice to the Team on making achievable Commitments and provide them fair warning when they start to accept a Card that will probably surprise them.
72. …need… a reliable way to measure the increased value contribution of the Team sprint-over-sprint
73. …so that… I can compare the Team’s rate of value contribution increase to the changes in revenue we are generating and adjust our direction if the value that I estimated isn’t being realized.
87. …need… a metric that informs me of the margin of error when the Teamcommits to a body of work
88. …so that… I can use this margin of error to predict reliable dates, and know when it is safe to lobby for a higher Commitment at each Planning Meeting.