Fishbone diagram

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 5: Line 5:
  
 
==The Purpose of the Fishbone Diagram==
 
==The Purpose of the Fishbone Diagram==
 
+
The purpose of the fishbone diagram in risk management is to identify various root causes of a potential problem for a project or program<!--Ref-->. 
  
 
==Application of the Fishbone Diagram==
 
==Application of the Fishbone Diagram==

Revision as of 16:10, 18 September 2017

The Fishbone diagram is named for its resemblance to a fishbone with the investigated problem being in the place of the head and the identified root causes coming out of the spine (see picture). It is also called an Ishikawa diagram after its creator Kaoru Ishikawa or a Cause-and-Effect diagram. Identifying the root causes of a problem makes it a valuable tool in Risk Management, as it can help the team figuring out how best to handle this with ARTA.

This article will focus on the fishbone diagram. It will consider how the diagram is appropriately used in Risk Management as well as its purpose ans limitations. It will also touch upon tools that can be used in conjunction with the diagram to strengthen a project's management of risks. The article will be based on previous literature on the subject.

Contents

The Purpose of the Fishbone Diagram

The purpose of the fishbone diagram in risk management is to identify various root causes of a potential problem for a project or program.

Application of the Fishbone Diagram

The Team

Common ways it is used

Limitations of the Fishbone Diagram

What the tool will not achieve

Tools it is often used in conjunction with to achieve the end goal

Suggested literature not covered by the DTU License

References

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox