Fishbone diagram
From apppm
(Difference between revisions)
| Line 11: | Line 11: | ||
===The Team=== | ===The Team=== | ||
===Common ways it is used=== | ===Common ways it is used=== | ||
| − | + | <!--References from City process, wikipedia, wong, Harvey-Maylor--> | |
==Limitations of the Fishbone Diagram== | ==Limitations of the Fishbone Diagram== | ||
| − | + | <!--References from Wong et al.; conclusion from Carmen Ciocoiu; conclusion from Journal of Medical Case reports; and ... could also be something like: it is emphasised that the tool is used in teams (ref) to better identify all causes this means that ...; --> | |
===What the tool will not achieve=== | ===What the tool will not achieve=== | ||
===Tools it is often used in conjunction with to achieve the end goal=== | ===Tools it is often used in conjunction with to achieve the end goal=== | ||
==Suggested literature not covered by the DTU License== | ==Suggested literature not covered by the DTU License== | ||
| − | + | <!-- Ishikawa original works; ...--> | |
==References== | ==References== | ||
Revision as of 21:18, 17 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. It is a valuable tool in Risk Management
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 |
