This fishbone diagram is the first draft that was put together as a team. Each one of these items on the fishbone diagram ended up on my project plan with start and end dates, action owners and predecessors. Some of the items on the fishbone diagram might seem obvious, but as a project manager who had no experience or knowledge in the information system field, this tool helped me identify all the "softer" actions I needed to take to ensure a successful project. On the Machine bone, we identified that we needed "organized access to both systems for members of the core team." And so on and so forth.
#Project planning tools fishbone update#
In the head of the fish, the project team put the desired outcome (effect), which in this case was simply "SAP to Ellipse Project Successful." Looking at the generic causes (the bones), the team initially identified 13 critical aspects that needed to be in place to achieve a successful outcome of the project.įor example, under the Measurement bone, the team identified that we needed to have a regular project steering committee every two weeks with the project sponsor to update him on the project and resolve risks and issues.
![project planning tools fishbone project planning tools fishbone](https://upload.wikimedia.org/wikipedia/commons/thumb/a/af/Cause_and_effect_diagram_for_defect_XXX.svg/1200px-Cause_and_effect_diagram_for_defect_XXX.svg.png)
To achieve this, I organized a session with the core team of the project and we created a reverse fishbone diagram to help identify all the critical aspects that had to be in place to ensure a successful project. The Execution of the Reverse Fishbone Diagram This was all well and good and covered what I like to call the "hard" aspect of the project, but I also wanted to ensure that the project was going to be successful from a "softer" perspective (people, processes, culture, etc.). A project plan was put in place by the information specialists for the transfer of data from SAP into Ellipse.
#Project planning tools fishbone full#
Without going into too many details of the project, let’s say this required a full team of three information specialists and a core team of five other part-time members. The project objective was to transfer data from a SAP system into an Oracle-based system called Ellipse. The concept of the reverse fishbone diagram was applied to a project I was leading for Metronet Rail (Metronet Rail looks at maintaining part of the London Underground).Īfter the integration of one business unit into another one within Metronet, the information systems of those two business units needed to be consolidated. You put the solution or outcome in the head (effect) of the fishbone diagram and ask yourself, what do I need in place to ensure this solution or outcome is met? The answers will then be split between the bones, helping you put a better-rounded project plan.īelow is an example of the application of the reverse fishbone diagram concept.
![project planning tools fishbone project planning tools fishbone](https://image4.slideserve.com/8299143/risk-analysis-fishbone-tool-l.jpg)
![project planning tools fishbone project planning tools fishbone](https://0901.static.prezi.com/preview/v2/atop2ytfonn5aqhotwojinjbul6jc3sachvcdoaizecfr3dnitcq_3_0.png)
In my case, I use the fishbone diagram for solutions and outcomes as well however, I call it the reverse fishbone diagram. The Reverse Fishbone Diagram-A Case Study For example, if In the fishbone diagram the effect is "Poor Quality," one of the causes below the Manpower bone might be "Lack of Training." Once you have your effect, you then can start identifying what the causes are behind that effect. Kaouru Ishikawa (1915-1989), a renowned Japanese engineer, identified the generic causes in the fishbone diagram as the six Ms: Machines, Manpower (people), Methods (Processes), Mother Nature (Environment), Money and Measurement. The head of the fishbone diagram is the effect the bones (typically six) in the fishbone diagram are the generic causes behind every effect.
![project planning tools fishbone project planning tools fishbone](https://thumbs.dreamstime.com/z/fishbone-diagram-ishikawa-methodology-infographic-scheme-missed-deadline-measurements-materials-personnel-environment-methods-203442770.jpg)
For more recent articles on process improvement and operational excellence, check our latest articles.Ī fishbone diagram helps identify the cause and effect relationship that exists in every system.