Difference between revisions of "Five whys"
Jump to navigation
Jump to search
m (terse/full) |
(→Sources: += InfoQ » Savita Pahuja » Limitations of Five Whys Technique in Agile Retrospective) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|goal=find the root cause of about anything | |||
|stage=Sparkle | |stage=Sparkle | ||
|theme=Agile, Lean | |theme=Agile, Lean | ||
| Line 15: | Line 16: | ||
*[http://www.youtube.com/watch?v=U3w_eIa7Eq0 5 Why], YouTube (funny?). | *[http://www.youtube.com/watch?v=U3w_eIa7Eq0 5 Why], YouTube (funny?). | ||
*[http://blogs.hbr.org/cs/2012/09/the_power_of_defining_the_prob.html HBR » The Power of Defining the Problem] | *[http://blogs.hbr.org/cs/2012/09/the_power_of_defining_the_prob.html HBR » The Power of Defining the Problem] | ||
*{{web|url=http://theitriskmanager.wordpress.com/2013/12/30/ten-ways-of-five-whys/|site=The IT Risk Manager|person=Chris Matts|title=Ten Ways of “Five Whys”}} | |||
*[http://www.infoq.com/news/2015/02/five-why InfoQ » Savita Pahuja » Limitations of Five Whys Technique in Agile Retrospective] | |||
{{Source}} | {{Source}} | ||
Latest revision as of 09:14, 1 March 2015
…any undertaking, entrepreneurial effort, or other collective initiative facing a tough impediment.
✣ ✣ ✣
Get to the root cause and fix it.
Therefore:
Ask “Why” five times and design a few experiments
✣ ✣ ✣
Also, see stretch and squeeze.
✣ ✣ ✣
Sources
- Root Cause Analysis From Juran, about the Jefferson Memorial, Washington.
- HBR » 5 Whys, Eric Ries (video 3:13)
- 5 Whys - Root Cause Analysis
- 5 Why, YouTube (funny?).
- HBR » The Power of Defining the Problem
- The IT Risk Manager » Chris Matts » Ten Ways of “Five Whys”
- InfoQ » Savita Pahuja » Limitations of Five Whys Technique in Agile Retrospective