Dantotsu: from bug to best coding practice

How to eradicate bugs and decrease their number over time?

This presentation introduces the Dantotsu method, its radical impact on quality, and how to implement it in tech companies.

learn more -->

Transcript

1. Dantotsu Radical Quality in Tech 1
2. Flavian Hautbois Co-author of the upcoming "Build to Sell" book Lean coach in Tech & Product 2 @flavianhautbois /in/flavianhautbois https://buildtosell.org contact@buildtosell.org - A technology geek - Passionate about how to create great digital products with lean thinking
3. Bugs are the norm in our industry 3 70 bugs 1000 lines of code Sources - The Economics of Software Quality (Capers Jones and Olivier Bonsignour), Carogalix study 7 to 25% of bug fixes introduce a brand new bug…
4. 4 Higher quality Higher productivity Faster delivery Higher customer satisfaction Higher sales Less cost Higher margins
5. The reason : a misconception that non-quality is less expensive than quality 5 Source: The economics of software quality
6. defect 0
8. The inspiration for radical quality in tech 8 2006-2015
9. Radical quality approach – 8-step procedure of the Team Leader 9 Check defective part Impact analysis and sorting Investigate cause Implement countermeasures Report in Asaichi Meeting Create / improve standards & deploy horizontally Train people Check through go and sees same day same day same day same day next day next day next day next day
10. Speed… is key 10 in 24h
11. Ocus example 11
12. 12 Weekly quality meeting
13. Let’s walk through 1 QRQC - describing the problem 3. EXPERIMENTS @ Sipios & Ocus 13
14. Let’s walk through 1 QRQC - describing the solution 3. EXPERIMENTS @ Sipios & Ocus 14
15. Let’s walk through 1 QRQC - describing the thought process & leadership actions 3. EXPERIMENTS @ Sipios & Ocus 15
16. AutoRABIT CodeScan example 16
17. AutoRABIT CodeScan example 17
18. 18 Daily quality meeting
19. AutoRABIT CodeScan example 19
20. Fishing for weak points 20 CodeScan infrastructure How to deploy the infrastructure (SRO) Which branch maps to the infrastructure + its environment (Engineering) Clarity of what is the app / what is a worker in CodeScan (SRO) CodeScan infrastructure Important change from SRO not communicated to CodeScan (SRO / Engineer) about the SES keys – but unclear why it had to be shared Quality test plan Have a test plan that covers most of the actual user cases (Engineering) How QA tests SAML QA plan to handle on-prem version
21. 21 Key points Top management buy-in Measure & set targets Train on Problem Solving Focus on tech learnings
22. 22 A template to get your started : the Ocus version