Why Software Gets In Trouble
Why Software Gets In Trouble
Software Quality Series: Vol. 2
About the Book
Lyndon Vrooman wrote what many readers have said about the effect "Why Software Gets In Trouble" had on him: "I'll be honest, about half way through this book, I thought that I found it rather bland and full of things that I was already doing. This changed however as I was assessing an application that I had been working with for years and we had found some critical faults in. I started thinking more about the book and the contents of it. After re-reading it, I realized that I hadn't been looking closely enough for faults, only going just beneath the skin. As I started to apply more and more of the information within, I began to realize more and more of what I had been learning was adding tremendously to the quality of the product. In short, after thinking more and more about this book, it's quickly gone to one that I recommend to everyone that I work with."
Another reviewer, Joe Strazzerel recounted the contents: "Jerry describes many of the ways errors occur, the correct way of thinking about errors (such as "Errors are not a moral issue" and "Quality is not the same thing as absence of errors"), how companies and processes get into a state where errors are more likely to occur (increased pressure, high levels of stress, poor estimation, lack of control, etc), and the effects of breakdowns."
"This book is fairly short, yet surprisingly thorough over its seven chapters:Chapter 1: Observing and Reasoning About ErrorsChapter 2: The Failure Detection CurveChapter 3: Locating The Faults Behind The FailuresChapter 4: Fault Resolution DynamicsChapter 5: Power, Pressure, and PerformanceChapter 6: Handling Breakdown PressureChapter 7: What We've Managed To Accomplish""For me, this was a very timely book. My team is going through some of the same pressure patterns Jerry writes about. For virtually every point made, I found myself saying 'I remember when that happened,' and sometimes 'That's happening right now!'""If you are a Software Testing professional, you should read this book. You should then give a copy to your manager, and to your manager's boss. Then, be prepared to discuss with them the realities of software development from a tester's point of view. After reading 'Why Software Gets In Trouble." you'll almost certainly have a more enlightened (and hopefully more receptive) audience."
And Don Gray wrapped up by adding in his review with a case example from one of his clients: "After three quarterly 'successful' releases a company had 453 defects opened in a single day against the 'successful' releases."
"Many books exist for any given programming language. Every developer had two or three at their desk. One book on software engineering may exist for every 100 language books. Maybe not. I noticed one developer had one.""453 defects don’t suddenly happen. Something in the process and culture allowed them to build until they could no longer be ignored. It seems to me someone at the company might benefit from learning about system dynamics and the reasons behind software errors.""Why Software Gets in Trouble is the only book I know of that explores the systemic dynamics and reasons behind software errors. Using stories, graphs and Diagrams of Effects, this book explores how different software cultures: * notice and think about errors * detect failures * locate the faults behind the errors * resolve faults * apply and handle pressure"The content applies to both managers and developers. If you’ve wondered why you keep experiencing the same patterns concerning shipping software, this book will help you understand why.""NOTE: If you’ve not read How Software is Built, you might find reading Why Software Gets in Trouble's appendices on Diagrams of Effects and Software Engineering Cultural Patterns helpful prior to starting the main text."
- Why Software Gets In Trouble
- New Preface
Part IV. Fault Patterns
Chapter 1: Observing and Reasoning About Errors
1.1. Conceptual Errors About Errors
- 1.1.1. Errors are not a moral issue
- 1.1.2. Quality is not the same thing as absence of errors
- 1.1.3. The terminology of error
1.2. Mis-classification of Error-Handling Processes
- 1.2.1. Detection
- 1.2.2. Location
- 1.2.3. Resolution
- 1.2.4. Prevention
- 1.2.5. Distribution
1.3. Observational Errors About Errors
- 1.3.1 Selection Fallacies
- 1.3.2. Getting observations backwards
- 1.3.3. The Controller Fallacy
- 1.4. Helpful Hints and Suggestions
- 1.5 Summary
- 1.6. Practice
- 1.1. Conceptual Errors About Errors
Chapter 2: The Failure Detection Curve
2.1 The Difference Detection Dynamic
- 2.1.1 The Root-Drew fallacy in difference detection
- 2.1.2 Why we misestimate failure detection
- 2.1.3 The bad news about the failure detection curve
2.2. Living With the Failure Detection Curve
- 2.2.1 The Failure Detection Curve as predictor
- 2.2.2 Undermining test coverage
- 2.2.3. Late finishing modules
- 2.3. Helpful Hints and Suggestions
- 2.4 Summary
- 2.5. Practice
- 2.6 Chapter Appendix
- 2.1 The Difference Detection Dynamic
Chapter 3: Locating The Faults Behind The Failures
3.1 The Dynamics of Fault Location
- 3.1.1 Direct effects of system size
- 3.1.2 Divide and Conquer to beat Size/Complexity
- 3.1.3 Divide the labor to beat delivery time
- 3.1.4 Indirect effects of system size
- 3.2 Circulation of STIs Before Resolution
- 3.3 Process Faults: Losing STIs
- 3.4 Political Time: Status Walls
- 3.5 Labor Lost: Administrative Burden
- 3.6 Helpful Hints and Suggestions
- 3.7 Summary
- 3.8. Practice
- 3.1 The Dynamics of Fault Location
Chapter 4: Fault Resolution Dynamics
4.1 Basic Fault Resolution Dynamics
- 4.1.1. Size/Complexity Dynamics
- 4.1.2 Side Effects
4.2 Fault Feedback Dynamics
- 4.2.1 The Fault Feedback Ratio (FFR)
- 4.2.2 The impact of FFR
- 4.2.3 Having an impact on FFR
- 4.2.4 A self-invalidating model
4.3 Deterioration Dynamics
- 4.3.1. Maintainability must be maintained
- 4.3.2 The ripple effect
- 4.3.3 Destruction of black box design integrity
- 4.3.4. The ripple effect over time
- 4.3.5. The Titanic Effect
- 4.3.6. Maintaining maintainability
- 4.4 Helpful Hints and Suggestions
- 4.5 Summary
- 4.6. Practice
- 4.1 Basic Fault Resolution Dynamics
Chapter 5: Power, Pressure, and Performance
5.1 The Pressure/Performance Relationship
- 5.1.1 The linear model
- 5.1.2. The burnout non-linear model
- 5.1.3. The collapse non-linear model
- 5.2 Pressure To Find “The Last Fault”
- 5.3 Stress/Control Dynamic
5.4 Forms of Breakdown Under Pressure
- 5.4.1 The Pressure/Judgment Dynamic
- 5.4.2 The Lost Labor Dynamic
- 5.4.3 The Pile-On Dynamic
- 5.4.4 The Panic Reaction
5.5 Management of Pressure
- 5.5.1. The self-regulating worker
- 5.5.2. The disempowering manager
- 5.5.3. The Law of Diminishing Response
- 5.5.4. The responsive manager
- 5.6 Helpful Hints and Suggestions
- 5.7 Summary
- 5.8. Practice
- 5.1 The Pressure/Performance Relationship
Chapter 6: Handling Breakdown Pressure
6.1 Shuffling Work
- 6.1.1 Task splitting
- 6.1.2 Everything is Number One Priority
- 6.1.3 Choosing your own priority
- 6.1.4 Doing the easiest task first
- 6.1.5 Circulating hot potatoes
6.2 Ways of Doing Nothing
- 6.2.1 Accepting poor quality products
- 6.2.2 Not accepting schedule slippage
- 6.2.3 Accepting resource overruns
- 6.2.4 Managers not available
- 6.2.5 No time to do it right
6.3 Short-Circuiting Procedures
- 6.3.1 The Boomerang Effect
- 6.3.2 The decision to ship poor quality
- 6.3.3 Bypassing quality assurance
- 6.3.4 Emergencies and interruptions
- 6.3.5 Morale effects
- 6.3.6 Managers are human
6.4 How Customers Impact the Boomerang
- 6.4.1 More failure reports
- 6.4.2 Multiplying costs after release
- 6.4.3 Increased temptation
- 6.4.4 The final solution
- 6.5 Helpful Hints and Suggestions
- 6.6 Summary
- 6.7. Practice
- 6.1 Shuffling Work
Chapter 7: What We’ve Managed To Accomplish
- 7.1. Why Systems Thinking?
- 7.2. Why Manage?
7.3. Estimating Our Accomplishments
- 7.3.1. Productivity increases
- 7.3.2. Why we’re suckers for magic bullets
- 7.3.3. Pattern 1 productivity; Pattern 2 ambition
7.4 What Each Pattern Has Contributed
- 7.4.1. Pattern 0: Oblivious
- 7.4.2. Pattern 1: Variable
- 7.4.3. Pattern 2: Routine
- 7.4.4. Pattern 3, 4, and 5
- 7.5. Meta-patterns
- 7.6 Helpful Hints and Suggestions
- 7.7 Summary
- 7.8 Practice
- Appendix A: The Diagram of Effects
Appendix B: The Software Engineering Cultural Patterns
- Pattern 0. Oblivious Process
- Pattern 1: Variable Process
- Pattern 2: Routine Process
- Pattern 3: Steering Process
- Pattern 4: Anticipating Process
- Pattern 5: Congruent Process
- Chapter 1: Observing and Reasoning About Errors
- What Next?
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers), EPUB (for phones and tablets) and MOBI (for Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
El Manual del ManagerKeyvan Akbary, Félix López, and Álvaro Salazar
¿Has deseado alguna vez el haber tenido una buena introducción al rol del Engineering Manager? En este libro aprenderás lo necesario para ejercer el rol de una manera efectiva: Expectativas y Responsabilidades del Rol, 1-1s, Ayudar a Crecer, Objetivos, Planes de Carrera, Cultura, Feedback, Contratación, Cultura de Producto y mucho más.
Ansible for KubernetesJeff Geerling
Ansible is a powerful infrastructure automation tool. Kubernetes is a powerful application deployment platform. Learn how to use these tools to automate massively-scalable, highly-available infrastructure.
Functional Design and ArchitectureAlexander Granin
Software Design in Functional Programming, Design Patterns and Practices, Methodologies and Application Architectures. How to build real software in Haskell with less efforts and low risks. The first complete source of knowledge.
CCIE Service Provider Version 4 Written and Lab Exam Comprehensive GuideNicholas Russo
The service provider landscape has changed rapidly over the past several years. Networking vendors are continuing to propose new standards, techniques, and procedures for overcoming new challenges while concurrently reducing costs and delivering new services. Cisco has recently updated the CCIE Service Provider track to reflect these changes; this book represents the author's personal journey in achieving that certification.
CCIE SP v4.1 - WorkbookŁukasz Bromirski, Piotr Jablonski, and Nicholas Russo
Are you striving to prepare to and pass CCIE SP lab exam? Take the opportunity and get this workbook! With the attached initial cfg files you will prepare yourself for the CCIE SP exam as well as learn SP technologies applicable to all kinds of today modern networks! This workbook covers blueprint topics and provides challenging examples.
Ansible for DevOpsJeff Geerling
Ansible is a simple, but powerful, server and configuration management tool. Learn to use Ansible effectively, whether you manage one server—or thousands.
Code Faster in DelphiAlister Christie
This book will make you a faster Delphi developer, it doesn't matter if you are just starting out, or have been using Delphi since version 1, you will find all sorts of tips, tricks and hacks to boost your productivity.
R Programming for Data ScienceRoger D. Peng
This book brings the fundamentals of R programming to you, using the same material developed as part of the industry-leading Johns Hopkins Data Science Specialization. The skills taught in this book will lay the foundation for you to begin your journey learning data science. Printed copies of this book are available through Lulu.
Composing SoftwareEric Elliott
All software design is composition: the act of breaking complex problems down into smaller problems and composing those solutions. Most developers have a limited understanding of compositional techniques. It's time for that to change.
The Hundred-Page Machine Learning BookAndriy Burkov
Everything you really need to know in Machine Learning in a hundred pages.
11 BooksIn this bundle, you will find 10 different agile books. They are about different aspects of being agile. - finding a job - doing coding dojo's - Retrospectives - Personal kanban - a non-typical coaching book and even a book that gives you an insight in the lives of some agile people.
WTFlop 6M + HU - Beta Bundle
Fifty Quick Ideas
3 BooksGet all three books for the price of two! Fifty Quick Ideas books are full of practical, real-world techniques that you can use to improve teamwork, build better products and build them in a better way.
Growing Agile: Coach's Guide Series
4 BooksThis bundle provides a collection of training and workshop plans for a variety of agile topics. The series is aimed at agile coaches, trainers and ScrumMasters who often find themselves needing to help teams understand agile concepts. Each book in the series provides the plans, slides, handouts and activity instructions to run a number of...
Marionette.js A to Z
Build A Better Backbone App
3 BooksThe best way to learn new development skills is through experience, but that takes time you don't have.Get the best of both worlds with this bundle: you'll learn how to produce modern web applications by learning from experienced developers like Derick Bailey and David Sulc. BackboneJS is one of the favorite tools on the web today, but it...
People Skills—Soft but Difficult
7 BooksPerhaps you've been told that "lack of people skills" has been holding you back. No wonder: you may have had hundreds of hours of technical training, but little or no "people skills" guidance.You've heard it said that people skills are "soft," whereas technical skills are "hard." For you, though, technical skills are "easy," but people skills...
SurviveJS - Webpack + React
2 BooksGet both SurviveJS - Webpack and SurviveJS - React for a single price!
Experiential Learning Bundle
4 BooksThis bundle provides all four volumes of the popular Experiential Learning Series at a savings of $20 over the price if purchased separately.