do faster releases improve software quality?
TRANSCRIPT
- 1. 1
2. 2 3. 52 weeks release cycle time 6 weeks release cycle time 30 25Number of Releases 20 15 10 5 02004 2005 2006 2007 2008 2009 2010 2011 20122013 Year 3 4. 4 5. Speed Quality5 6. Case Study 20 Alpha 5 Alpha 20 Beta 5 Beta 23 Minor 6 Minor 2 Major 5 Major 6 7. Median Daily Crash Count(lower is better) Median Uptime(higher is better) 7 8. 1320Number of Post Release Bugs /543 Day210Traditional Release (TR) Rapid Release (RR)8 9. 250KMedian Daily Crash Count 200K 150K 100K 50K0KTraditional Release (TR) Rapid Release (RR)9 10. 1200 1080960Median Uptime in Seconds8407206004803602401200Traditional Release (TR) Rapid Release (RR)10 11. YES BUTMore investigations are needed11 12. Fixing time of bugs (lower is better) 12 13. 100% 90% 80% 70%% of Bugs Fixed 60% 50% 40% 30% 20% 10%0% Traditional Release Rapid Release (RR) - Traditional Release Rapid Release (RR) - (TR) - MainMain(TR) - BetaBetaMain Releases Beta Releases13 14. 654159100 90 80 70Bug Age in Days 60 50 40 30 20 100Traditional Release (TR) Rapid Release (RR)14 15. 15 16. 16 17. 4.05.0 6.0 7.0 8.0 9.0100% 90% Version8 80% Version7% of Stale Crash Reports 70% 60% Version6 50% Version5 40% 30% Version4 20% Version3.6 10% 0% 012345678901234567012345678012345601234501234Weeks since Last ReleaseApproximately 20% of users remain on a stalled version 17 18. 18 19. 19 20. 20