Process — Managing Technical Aspects →mediumMultiple ChoiceObjective-mapped

PMP Process — Managing Technical Aspects Practice Question

A project team is implementing a new software feature. During testing, a critical defect is found that could delay the release. The project manager needs to determine the root cause. Which tool or technique should be used?

⚠ Common exam trap

Many exam-takers confuse root cause analysis tools with quality control tools, mistakenly selecting scatter diagrams or control charts because they associate them with defect analysis, but only the cause-and-effect diagram directly structures the search for underlying causes.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Cause-and-effect diagram

The cause-and-effect diagram (also known as a fishbone or Ishikawa diagram) is the correct tool for root cause analysis because it systematically maps potential causes of a defect across categories like people, process, technology, and environment. In this software testing scenario, the project manager would use it to brainstorm and visually trace the critical defect back to its underlying technical root cause, such as a coding logic error or integration failure, rather than just observing symptoms.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Scatter diagram
Why it's wrong here
A scatter diagram plots pairs of numerical data to determine if a correlation or relationship exists between two different variables, such as project cost and schedule deviation. While it can indicate the strength and direction of a relationship, it does not systematically break down a problem into its potential causal factors or identify the underlying reasons for a defect. Its primary utility is for correlation analysis, not for dissecting a problem to find its root cause.
✗
Control chart
Why it's wrong here
Control charts are statistical process control tools used to determine if a process is stable and in statistical control by monitoring performance over time against established upper and and lower control limits. They help identify out-of-control points or trends, signaling when a process needs investigation due to abnormal variation. However, a control chart itself does not perform the root cause analysis; it merely indicates when such an analysis might be necessary.
✗
Delphi technique
Why it's wrong here
The Delphi technique is a structured communication method used to obtain consensus from a panel of experts on a specific topic through a series of anonymous questionnaires and feedback rounds. While valuable for forecasting, risk identification, or decision-making where expert opinion is crucial, it is a group facilitation technique for opinion gathering, not a direct analytical tool for systematically dissecting a problem to identify its underlying causes. It relies on subjective expert judgment rather than objective causal analysis.
✓
Cause-and-effect diagram
Why this is correct
A cause-and-effect diagram, also known as an Ishikawa or fishbone diagram, is a visual tool used for systematically exploring all potential factors that could contribute to a specific problem or defect. It categorizes potential causes into major branches (e.g., Man, Machine, Material, Method, Measurement, Environment) to facilitate a comprehensive root cause analysis. This structured approach helps teams identify and investigate the underlying reasons for an issue, making it ideal for defect analysis and problem-solving.

Go deeper

PMP Process — Managing Technical Aspects Practice Question

Why each option matters

Option-by-option breakdown

Related to this question