Zero Bugs: State of the Practice
1 like472 views
The document discusses the concept of 'zero bugs' in software development, emphasizing the importance of building quality in during the development process rather than relying solely on testing afterward. It highlights various practices and tools related to coding, architecture, testing, and deployment, indicating a need for improvement in these areas to achieve higher quality outcomes. The author encourages collaboration, using innovative techniques, and enhancing skills to minimize defects in software products.
Zero Bugs: State of the Practice
- 1. Zero Bugs: State of the Practice Stephen Vance Agile Alliance Technical Conference April 21, 2017
- 4. Zero “Bugs”! • Why? vs. What? – Weinberg: “Faults” and “Failures” – There is rarely only one “why” even at the root – “Why” drives improvement • When? – Does it meet expectations, intentions, and needs? – Prior to release, it’s rework – After, it’s unrealized value © 2017 Stephen Vance Zero Bugs: State of the Practice 4
- 5. Frame of Reference • Lean – Focus on value – Seek perfection – Build feedback loops • Key waste types for software quality – Inventory – Waiting – Over-processing – Over-production – Defects https://www.lean.org/WhatsLean/Principles.cfm © 2017 Stephen Vance Zero Bugs: State of the Practice 5
- 9. What’s Typical? (Highly Subjective and Anecdotal) • Coding Practices – Limited to moderate use of pair programming with little mob programming – DSLs if they are supplied – Limited understanding of design patterns – Limited understanding of refactoring – OO as default with some functional constructs – Dynamic or strictly typed languages – Mostly test early with some TDD or BDD • Architecture – Little to no architecture or big up-front architecture • Tools – Low to moderate code coverage – Moderate use of static analysis – Code generation if supplied • Testing – Moderate to high manual testing – Increasing dev-test collaboration but still limited – Light to moderate use of exploratory testing – No to little use of advanced testing techniques like QuickCheck, fuzz, mutation • Build and Deploy – CI with some CD – Light to moderate application monitoring – Light to moderate DevOps and infrastructure as code – Moderate use of automated rolling deployment, heavily tied to use of cloud at scale © 2017 Stephen Vance Zero Bugs: State of the Practice 9
- 10. The Lean Quality Quotient™ (Not actually trademarked) • The degree to which a practice is used in a manner that is – Emergent – Iterative – Adaptive – Informed – Pre-emptive © 2017 Stephen Vance Zero Bugs: State of the Practice 10
- 11. © 2017 Stephen Vance Zero Bugs: State of the Practice 11 Architecture Architecture Pair Programming Mob Programming DSLs Design Patterns Refactoring OO Dynamically Typed Functional Strictly Typed Test Early 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Lean Quality Quotient Prevalence Coding Practices
- 12. © 2017 Stephen Vance Zero Bugs: State of the Practice 12 Code Coverage Static Analysis Code Generation 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Lean Quality Quotient Prevalence Tools
- 13. © 2017 Stephen Vance Zero Bugs: State of the Practice 13 Manual Testing Dev-Test Collaboration Exploratory Testing Advanced Testing 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Lean Quality Quotient Prevalence Testing
- 14. © 2017 Stephen Vance Zero Bugs: State of the Practice 14 Continuous Integration Continuous Delivery Application Monitoring DevOps Automated Deployment 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Lean Quality Quotient Prevalence Build and Deploy
- 15. © 2017 Stephen Vance Zero Bugs: State of the Practice 15 Architecture Architecture Pair Programming Mob Programming DSLs Design Patterns Refactoring OO Dynamically Typed Functional Strictly Typed Test Early Code Coverage Static Analysis Code Generation Manual Testing Dev-Test Collaboration Exploratory Testing Advanced Testing Continuous Integration Continuous Delivery Application Monitoring DevOps Automated Deployment 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Lean Quality Quotient Prevalence Composite
- 16. So What Next? • Do more testing • Figure out how to kill testing • Bring the skills to the front to build quality in • Extend the practicum – Real-world design patterns and refactoring – Evolutionary architecture • Enhance collaboration • Improve the tools • Use more tools © 2017 Stephen Vance Zero Bugs: State of the Practice 17
- 17. Should We …? • Create more DSLs and teach how to create good DSLs? • Move toward strong typing? • Move toward functional programming? • Do more mob programming? • Expand or eliminate code generation? • Teach the machines to do our jobs? © 2017 Stephen Vance Zero Bugs: State of the Practice 18
- 19. References • Crosby, Philip, “Quality is Free,” McGraw-Hill • Tarlinder, Alexander, “Developer Testing: Building Quality into Software,” Addison- Wesley • Thompson, Kate, “Zero Bugs and Program Faster,” Kate Thompson Publishing • Weinberg, Gerald M., “Errors: Bugs, Boo-boos, Blunders,” Leanpub © 2017 Stephen Vance Zero Bugs: State of the Practice 20
- 20. Informit.com/aatc Save 40% through April 30, 2017 • Use code AATC • Good on print & eBook • eBook files include PDF, EPUB, and MOBI Offer only good at informit.com/aatc 21
- 21. Contact Me Stephen Vance https://www.vance.com steve@vance.com @StephenRVance srvance on GitHub and LinkedIn © 2017 Stephen Vance Zero Bugs: State of the Practice 22