Quick Root Cause Analysis - Revision history

Mmusij at 23:22, 2 December 2018

2018-12-02T23:22:30Z

← Older revision		Revision as of 23:22, 2 December 2018
Line 4:		Line 4:

	This is particularly good for when a [[Sprint Retrospective\|Retrospective]] is not sufficient to dive into enough detail, and a more focussed approach is needed when a system failure has been experienced for example.		This is particularly good for when a [[Sprint Retrospective\|Retrospective]] is not sufficient to dive into enough detail, and a more focussed approach is needed when a system failure has been experienced for example.

			[[File:Quick_Root_Cause_Analysis.jpg\|500px\|Quick Root Cause Analysis]]

	==Learning Objectives==		==Learning Objectives==

Mmusij: /* See Also */

2018-12-02T23:10:12Z

Mmusij: /* See Also */

2018-12-02T23:09:43Z

Mmusij: Created page with "Category:Agile:WorkshopsCategory:Agile This is a quick method to do root cause analysis or the "5 Whys", and can be done just after a failure event that needs to unco..."

2018-12-02T23:09:30Z

Created page with "Category:Agile:Workshops Category:Agile This is a quick method to do root cause analysis or the "5 Whys", and can be done just after a failure event that needs to unco..."

New page

[[Category:Agile:Workshops]][[Category:Agile]]

This is a quick method to do root cause analysis or the "5 Whys", and can be done just after a failure event that needs to uncover the underlying causes and effects, and derive appropriate remedies.

This is particularly good for when a [[Sprint Retrospective|Retrospective]] is not sufficient to dive into enough detail, and a more focussed approach is needed when a system failure has been experienced for example.

==Learning Objectives==
* What are the underlying issues below the superficial and visible impacts, and what are appropriate remedies for them

==Timings==
Most conversations tend to go for an hour or so to really dig down and get an appropriate understanding of the underlying issues and possible remedies.

==Materials==
* Whiteboard or flip chart
* Whiteboard pens

==Tasks==
# In the bottom corner of the whiteboard or flip chart write out the symptom or the system failure that was experienced
# Next draw two small arrows leading into the symptom and ask the team what were the causes of the symptom
# Write in the causes described on the whiteboard as contributors to the symptom. (These are the 1st order causes or 1st Whys.)
# Next draw arrows into the 1st order causes and ask the team what causes contributed to those causes, and write them in. (These are the 2nd order causes or 2nd Whys.)
# Repeat until either the team cannot go any further or 5th order causes, (5 Whys,) have been identified.
# Next in a different colour, ask the team what remedies will fix the underlying causes and write those on the board.
# Finally, create an action list of what, when and who will do the actions needed to implement the changes and remedy the problems.

==See Also==
* [[Scrum Retrospective]]
* [[Kaizen & Continuous Improvement]]

← Older revision		Revision as of 23:10, 2 December 2018
Line 25:		Line 25:

	==See Also==		==See Also==
	* [[~~Scrum Retrospectives~~]]		* [[Sprint Retrospective]]
	* [[Kaizen & Continuous Improvement]]		* [[Kaizen & Continuous Improvement]]

← Older revision		Revision as of 23:09, 2 December 2018
Line 25:		Line 25:

	==See Also==		==See Also==
	* [[Scrum ~~Retrospective~~]]		* [[Scrum Retrospectives]]
	* [[Kaizen & Continuous Improvement]]		* [[Kaizen & Continuous Improvement]]