Controlling Quality in Software Development
summary
Argues quality is the balance of benefits versus risks and offers three concrete pillars: build the right thing, build it at the right time, build it the right way. Recommends controls from unit tests and property-based testing through integration and A/B experiments, type systems and even formal proofs, mapped to a risk/benefit chart. Shows a simple risk scoring (likelihood, impact, detection scored 1/4/7/10), prioritizes top risks, iterates mitigations, and measures whether controls actually reduce scores.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:24Three Little Pigs
- 11:46What Is the Right Way
- 19:18Technical Controls
- 19:39What Are the Types of Controls
- 20:01Manual Tests
- 21:10Unit Tests
- 23:59Integration Tests
- 27:39Benefits of Coming to this Conference
- 30:13Risk Statements
- 38:32Focus on the Key Risks
- 40:01Examples
- 41:08Extending Legacy Codes
- 45:23An Organization Will Produce Higher Quality Software if Its Employees Feel Respected
- 49:51Advantages of Tdd
related talks
19mHow can we improve quality on a project?
46mQuality Engineering for DevOps Teams
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)
01h 02mKEYNOTE: Quality Engineering Strategy to Grow From Testing to Built-in Quality
50mThe End of Testing as We Know It
28mInstilling the built-in quality mindset into a dev team
15mImprove continuous delivery by target quality aspects by your tests
35mWhy Software Engineers Should Make Quality a Priority