Slides from the lightning talk at the 36th Softwerkskammer Rhein-Main Meetup

1. 5-Whys technique
Determine the root cause of a problem
Alexei Vinogradov

2. Alexei Vinogradov
freiberuflicher IT-Berater
Test, Testmanagement, Testautomatisierung,
Coaching
email: alexei@vinogradov-it.de
skype: alexejv
twitter: @i_vino
https://www.softwerkskammer.org/groups/testing

3. Evolution
• We know what to change
• We know how to change
• We can do the work to the end
(c) Maxim Dorofeev http://2014.codefest.ru/lecture/887 (in Russian)

4. 5 Whys
• (What to change?)
• Problem-solving technique
• Toyota, Japan
• In 1920-ies

5. 5 Whys
• state a problem (or „unlucky circumstance“)
• iterative questioning to explore cause-effect
• looking for the root cause of a problem
• 5 iterations are typically enough

6. 5 Whys
Circumstance
Reason
Reason
Reason
Reason
Reason

7. 5 Whys
Server down
Hard drive full
Logs too big
No achrive hardw
Order not apprv
CEO on holiday

8. 5 Whys
Circumstance
Reason
Reason
Reason
Reason
Reason
Reason
Reason Reason
Reason Reason Reason
Reason
ass..les all aroundReason

9. 5 Whys
Service is down
added new feature on the last day
Product owner insisted
we’ve done in sprint everything wrong
we’re seeing PO infrequently
(c) Maxim Dorofeev http://2014.codefest.ru/lecture/887 (in Russian)

10. Tips
• Bring people together for analysis
• Write down the results live
• If not agreed - make multiple branches
• Go broad first, then prioritize branches

11. Summary
• The problems may live deeper than it seems
• Solving root cause brings more benefit than
curing symptoms
• People may understand same things differently
• Some well-known „old“ production techniques
are applicable for the IT world very well

12. The End.
Questions?
skype: alexejv
email: alexei@vinogradov-it.de
twitter: @i_vino