Fishbone diagram

A visual root-cause analysis tool that shows a stated problem at the head and organizes possible causes along branching 'bones' by category, allowing the team to drill down into sub-causes; also known as a cause and effect diagram.

Key Points

  • Clarifies the relationship between an effect (problem) and potential causes grouped by category.
  • Built through facilitated brainstorming; teams ask "why" repeatedly to add deeper sub-causes.
  • Typical categories include Methods, People, Materials, Equipment/Technology, Environment, and Measurement (adapt as needed).
  • Supports problem exploration; findings should be validated with data before selecting corrective actions.

Example

During Control Quality on a software project, the team faces recurring login failures. The project manager leads a fishbone (cause and effect) session. Categories include People, Process, Tools, Environment, and Requirements. The team maps sub-causes such as ambiguous acceptance criteria, flaky test environment, missing input validation, and skipped peer reviews. These insights guide targeted experiments and fixes.

PMP Example Question

During a quality review, a project team wants to structure and brainstorm potential reasons for a persistent defect before running experiments. Which tool should the project manager use?

  1. Pareto chart
  2. Fishbone diagram (cause and effect diagram)
  3. Control chart
  4. Scatter diagram

Correct Answer: B — Fishbone diagram (cause and effect diagram)

Explanation: A fishbone diagram is used to brainstorm and organize possible causes of a problem by category before validating them with data.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Become an AI-First Agile Leader!

HK School of Management and Technology helps you apply AI to Agile work with practical, prompt-based workflows for real-world Scrum challenges. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More