5-Whys technique Determine the root cause of a problem Alexei Vinogradov
Alexei Vinogradovfreiberuflicher IT-BeraterTest, Testmanagement, Testautomatisierung,Coaching
email: [email protected] skype: alexejvtwitter: @i_vinohttps://www.softwerkskammer.org/groups/testing
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)
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
5 WhysCircumstance
Reason
Reason
Reason
Reason
Reason
Reason
Reason Reason
Reason Reason Reason
Reason
ass..les all aroundReason
5 WhysService 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)
Tips
• Bring people together for analysis
• Write down the results live
• If not agreed - make multiple branches
• Go broad first, then prioritize branches
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
The End. Questions?
skype: alexejvemail: [email protected] twitter: @i_vino