Ishikawa diagram is a graphic technique, that is used for displaying the characteristics of a given situation or problem. It is also known as Fishbone Diagrams, Herringbone Diagrams, Cause-and-Effect Diagrams, or Fishikawa. Ishikawa diagrams are used for defect analysis (Root Cause Analysis). It is very useful when the analyzed defect has multiple causes. A problem or the defect statement is placed at the “head” of the diagram, and categories for grouping potential causal factors are placed as “bones.” This will be referred to as a “problem Ishikawa.” The technique is useful in brainstorming sessions to identify potential causes and areas for further investigation. It could be used in affinity diagram sessions too.
Ishikawa diagrams can also be an effective tool for communicating what essential factors are needed to achieve a positive outcome or result. As described here, this “positive Ishikawa” will have the desired effect at the “head” and categories of enablers or factors as the “bones”. You can use it in your Sprint Retrospective.
A Positive Ishikawa diagram can provide a beginning to solutions development. The diagram will show the factors needed to invent a new approach, new business philosophy, or achieve a goal. They are constructed in the same manner as a problem Ishikawa, except enablers replace causes and a desired effect or goal replaces the problem. This application of the technique can be quite useful, during goal setting or implementation planning. Actions to affect the required change can then be derived from reviewing the enablers.
This technique can also be used to analyze the causes of problems inherent in an activity flow. Use the activity flow as the backbone of the Ishikawa with the desired activity result (or output) at the “head.” For each activity on the flow, brainstorm possible causes (and/or enablers), and document them on the diagram radiating out from the activities.
Every industry uses fishbone diagrams; however, they may have a different categorization of causes. You need to customize the category to your requirements.
Alternatively, you may also use the five whys a technique or the 4 P’s (Product, Policies, Procedures, and Plant).
Example: Let’s try an example where the problem that needs our attention is wrong/delayed/damaged delivery.
The possible reasons are many, like faulty packaging that led to damage during transit, the wrong product being released for delivery, or the address label on the product wasn’t correct. We can classify the same in main causes and present it in the fishbone diagram like below:
Example: The team is not predictable. Never know when the product will be ready.
Q: What makes the team unpredictable?
C: Changes coming through all the time.
Q: Where do the changes come from?
C: Normally from the business, who is the visionary of the product, and a bit from our users, but those are usually minor changes.
Q: When is the most critical time?
C: When marketing wants insights in order to prepare campaigns, compliance with a federal mandate forces us to commit to a certain functionality several Sprints before the product launch.
Q: Who can influence that?”
C: Our Application Owner, who might be more present during the release and make his comments at every Sprint Review.
Q: Why is he not present at each Sprint Review?
C: He joined the first few reviews, but we didn’t deliver much functionality at that time, so he gradually stopped coming. Maybe it’s time to invite him again.
An Ishikawa Diagram is a vital tool in identifying the root cause as a visual representation of a problem. Although it is time-consuming, the benefits are enormous as instead of pointing out just one reason, this technique gives us all the possible reasons that assist not only in identifying the root cause of the current problem and avoiding any future mishappening.
This tool helps you remove the root cause of the problem and develop an understanding among team members. You use the fishbone diagram with a critical problem because you cannot spend time on every small issue.
Reference: Click Here
A well-maintained product backlog is crucial for successful product development. It serves as a single…
Incremental value to the customer refers to the gradual delivery of small, functional parts of…
A Product Market refers to the group of potential customers who might be interested in…
The Professional Agile Leadership - Evidence-Based Management (PAL-EBM) certification offered by Scrum.org is designed for…
The Professional Agile Leadership (PAL I) certification, offered by Scrum.org, is designed to equip leaders…
Choosing the right Scrum Master Certification depends on your current experience and career goals. If…