Retrospective Technique - 5 Whys

The 5 Whys is an iterative question-asking technique used to explore the cause-and-effect relationships underlying a particular problem.The primary goal of the technique is to determine the root cause of a defect or problem. (The "5" in the name derives from an empirical observation on the number of iterations typically required to resolve the problem.)

A key phrase to keep in mind in any 5 Why exercise is "people do not fail, processes do".
Source- 5 Whys

 Example- The vehicle will not start. (the problem)
  1. Why? - The battery is dead. (first why)
  2. Why? - The alternator is not functioning. (second why)
  3. Why? - The alternator belt has broken. (third why)
  4. Why? - The alternator belt was well beyond its useful service life and not replaced. (fourth why)
  5. Why? - The vehicle was not maintained according to the recommended service schedule. (fifth why, a root cause)

Comments

  1. Evan RaymondsAugust 21, 2019 at 2:32 AM

    Root cause analysis is highly benefited by 5 Whys, a diagram aid in cause-and-effect relationships underlying a particular problem. The primary goal of the technique is to determine the root cause of a defect or problem by repeating the question "Why?". Understanding 5 whys is easy with your explanation. You can start drawing 5 whys with these 5 whys analysis templates

    ReplyDelete

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros
Read more