Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
5-Whys technique
Determine the root cause of a problem
Alexei Vinogradov
Alexei Vinogradov

freiberuflicher IT-Berater



Test, Testmanagement, Testautomatisierung,

Coaching
email: alexei@vinogra...
Evolution
• We know what to change
• We know how to change
• We can do the work to the end
(c) Maxim Dorofeev http://2014....
5 Whys
• (What to change?)
• Problem-solving technique
• Toyota, Japan
• In 1920-ies
5 Whys
• state a problem (or „unlucky circumstance“)
• iterative questioning to explore cause-effect
• looking for the roo...
5 Whys
Circumstance
Reason
Reason
Reason
Reason
Reason
5 Whys
Server down
Hard drive full
Logs too big
No achrive hardw
Order not apprv
CEO on holiday
5 Whys
Circumstance
Reason
Reason
Reason
Reason
Reason
Reason
Reason Reason
Reason Reason Reason
Reason
ass..les all aroun...
5 Whys
Service is down
added new feature on the last day
Product owner insisted
we’ve done in sprint everything wrong
we’r...
Tips
• Bring people together for analysis
• Write down the results live
• If not agreed - make multiple branches
• Go broa...
Summary
• The problems may live deeper than it seems
• Solving root cause brings more benefit than
curing symptoms
• People...
The End.
Questions?
skype: alexejv

email: alexei@vinogradov-it.de
twitter: @i_vino
Nächste SlideShare
Wird geladen in …5
×

5-Whys Method

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

  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

5-Whys Method

  1. 1. 5-Whys technique Determine the root cause of a problem Alexei Vinogradov
  2. 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. 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. 4. 5 Whys • (What to change?) • Problem-solving technique • Toyota, Japan • In 1920-ies
  5. 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. 6. 5 Whys Circumstance Reason Reason Reason Reason Reason
  7. 7. 5 Whys Server down Hard drive full Logs too big No achrive hardw Order not apprv CEO on holiday
  8. 8. 5 Whys Circumstance Reason Reason Reason Reason Reason Reason Reason Reason Reason Reason Reason Reason ass..les all aroundReason
  9. 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. 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. 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. 12. The End. Questions? skype: alexejv
 email: alexei@vinogradov-it.de twitter: @i_vino

×