I will pay for the following article 647 W5 assign Fish Bone Diagram. The work is to be 4 pages with three to five sources, with in-text citations and a reference page.

I will pay for the following article 647 W5 assign Fish Bone Diagram. The work is to be 4 pages with three to five sources, with in-text citations and a reference page. 183). The diagram was noted to be useful during brain storming sessions, as well as in investigating the root cause of how the particular event turned out that way. Through scrutinizing sequence of transpired endeavors in clearly categorized elements, the diagram eventually assists in illuminating the cause and the ultimate effect/s of a challenging situation (American Society for Quality (ASQ), n.d.). The example of the fish bone diagram is shown in the figure below:

The fish bone tool can be used in project management through enabling project managers and the project management team to accurately identify potential risks in various facets of the project. As emphasized, there are “three categories of project risk are controllable known

risks, uncontrollable known risks, and unknown risks… Root cause analysis not only makes known project risks more understandable but also shows you how to manage each risk” (Kendrick, 2003, pp. 184-185). Thus, the fish bone tool enables enhancing awareness of project risks in various categories to develop strategies that would mitigate and manage these risks.

The fish bone tool is created following these prescribed six (6) steps: “(1) Draw Problem Statement. (2) Draw Major Cause Categories. (3) Brainstorm Causes. (4) Categorize Causes. (5) Determine Deeper Causes. and (6) Identify Root Causes” (Fishbone Diagram Cause and Effect Analysis, 2015). For the problem that was encountered by Great University (GU) in the previous paper, the system failure could be more closely evaluated using the fish bone diagram. The diagram is created with the six (6) steps and shown below:

Under brainstorming stage, the project manager and team members could think of all possible causes of the system failure using the major categories. These causes could be as simple, deep, bizarre, unique, or diverse, as members of the project team could think of.