You are the project manager of the NGH project for your organization. You want to create a causeand- effect diagram to help discover the root causes of the risks within the project. Harold, the CIO…

While cause-and-effect relationships are involved, choice A incompletely describes the diagram as only a graphical representation of situations and misses the defining purpose of root cause identification.

An Ishikawa diagram is the same tool as a cause-and-effect diagram (also called a fishbone diagram), named after quality expert Kaoru Ishikawa who developed it. Since the project manager already proposed creating a cause-and-effect diagram to find root causes, Harold's recommendation to use an Ishikawa diagram is functionally identical - there is no difference between the two. Both are used to trace contributing factors back to their root causes.

A diagram that shows how elements of a system interrelate describes an influence diagram, not an Ishikawa diagram.

Diagramming risks according to the work breakdown structure describes a risk breakdown structure (RBS), which is a different tool from an Ishikawa diagram.