Discuss PMI PMI-PBA Exam Topic 2 Question 96

Through user acceptance testing, a software flaw was identified. What should the business analyst do next as part of the root cause analysis in order to analyze and resolve the discrepancy?

ACreate a fishbone diagram.

BCreate an interface analysis.

CCreate a Delphi estimation.

DCreate a functional decomposition.

Suggested Answer: A

A fishbone diagram, also known as a cause-and-effect diagram or an Ishikawa diagram, is a tool that helps to identify and analyze the possible causes of a problem or an effect. It can help the business analyst to perform a root cause analysis in order to analyze and resolve the discrepancy identified through user acceptance testing. A fishbone diagram has a structure that resembles a fish skeleton, with a head, a spine, and several branches. The head represents the problem or the effect, the spine represents the main cause categories, and the branches represent the sub-causes or factors that contribute to the problem or the effect. By creating a fishbone diagram, the business analyst can brainstorm and organize the potential causes of the software flaw, and then investigate and verify the most likely root cause. A fishbone diagram can also help to communicate the findings and recommendations to the stakeholders and the development team. An interface analysis is a tool that helps to identify and describe the interactions and dependencies between different components or systems. It does not help to perform a root cause analysis in order to analyze and resolve the discrepancy identified through user acceptance testing, as it does not focus on the causes and effects of the problem. A Delphi estimation is a tool that helps to obtain a consensus among a group of experts on a complex or uncertain issue. It does not help to perform a root cause analysis in order to analyze and resolve the discrepancy identified through user acceptance testing, as it does not provide a systematic and structured way to identify and analyze the causes of the problem. A functional decomposition is a tool that helps to break down a complex system or process into smaller and simpler components or functions.It does not help to perform a root cause analysis in order to analyze and resolve the discrepancy identified through user acceptance testing, as it does not show the relationships and influences between the components or functions.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, PMI Guide to Business Analysis2, Business Analysis for Practitioners: A Practice Guide3, Root Cause Analysis: Definition, Examples & Methods | Tableau1

Get Premium PMI-PBA Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

32 comments · newest first

Eve 11 months ago

I didn't know a fishbone diagram was so effective! Surprised!

Van 11 months ago

Wait, a Delphi estimation? That seems off for this situation.

Julieta 12 months ago

Definitely go with the fishbone! It's a classic for a reason.

Isadora 12 months ago

I think an interface analysis would be more relevant here.

Annelle 1 year ago

A fishbone diagram is super helpful for root cause analysis!

Vilma 1 year ago

I definitely remember that the fishbone diagram is a common tool for root cause analysis, so I might lean towards that option.

Louisa 1 year ago

I’m a bit confused about the options. I feel like an interface analysis could be relevant, but I can't recall exactly how it fits into root cause analysis.

Viola 1 year ago

I remember practicing a question where we had to analyze discrepancies, and I think a functional decomposition might be useful too.

Billy 1 year ago

I think creating a fishbone diagram could help identify the root causes, but I'm not entirely sure if that's the best first step.

Colette 1 year ago

A Delphi estimation? I'm not sure that's the right tool for this type of problem. I'd lean more towards a functional decomposition to break down the issue and identify the root cause.

Nobuko 1 year ago

Okay, let's see. The key here is to analyze and resolve the discrepancy, so I think creating an interface analysis would be the best approach to really understand how the different components are interacting.

Fausto 1 year ago

Hmm, I'm a bit unsure about this one. I'm not super familiar with the different root cause analysis techniques, so I'll have to think this through carefully.

Dalene 1 year ago

This seems like a straightforward root cause analysis question. I'd go with creating a fishbone diagram to really dig into the potential causes of the software flaw.

Terrilyn 2 years ago

Delphi estimation, huh? Sounds like we're about to summon the Oracle of Delphi to solve this software mystery. All we need is some toga-wearing philosophers and a talking snake.

Delmy 2 years ago

↳ replying to Terrilyn

B) Create an interface analysis.

Samuel 2 years ago

↳ replying to Terrilyn

A) Create a fishbone diagram.

Emile 2 years ago

I'd say a fishbone diagram is the way to go. It's like doing a full-body checkup on that software flaw. Gotta get to the heart of the matter!

Alease 2 years ago

I believe a Delphi estimation might provide us with a more accurate analysis of the root cause.

Sherita 2 years ago

Functional decomposition, all the way! Break that problem down into bite-size pieces, easy peasy.

Jeffrey 2 years ago

Interface analysis? Nah, that's not gonna cut it. We need to dig deeper, like a Delphi estimation or functional decomposition.

Leila 2 years ago

↳ replying to Jeffrey

True, let's use multiple methods to ensure we cover all angles in our analysis.

Brent 2 years ago

↳ replying to Jeffrey

I think a fishbone diagram could also be useful in identifying all possible causes.

Jamie 2 years ago

↳ replying to Jeffrey

I agree, a functional decomposition could also give us a better understanding of the issue.

Tyisha 2 years ago

↳ replying to Jeffrey

Let's go with a Delphi estimation, it might help us uncover the root cause.

Curtis 2 years ago

Hmm, a fishbone diagram seems like the way to go. Gotta get to the root of that pesky software flaw!

Elvera 2 years ago

↳ replying to Curtis

D) Let's get to the bottom of this issue and find a solution.

Lera 2 years ago

↳ replying to Curtis

C) Once we have the diagram, we can start analyzing the different factors.

Artie 2 years ago

↳ replying to Curtis

B) I agree, it's a great tool for identifying root causes.

Agustin 2 years ago

↳ replying to Curtis

A) Create a fishbone diagram.

Myrtie 2 years ago

I think creating a functional decomposition could also be helpful in understanding the discrepancy.

Jamal 2 years ago

I agree with Fairy, a fishbone diagram can help us identify the causes of the software flaw.

Fairy 2 years ago

I think we should create a fishbone diagram to analyze the root cause.

PMI-PBA Exam - Topic 2 Question 96 Discussion