Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

PMI Exam PMI-PBA Topic 2 Question 96 Discussion

Actual exam question for PMI's PMI-PBA exam
Question #: 96
Topic #: 2
[All PMI-PBA Questions]

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?

Show Suggested Answer Hide Answer
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


by Lynette at Jan 28, 2025, 06:22 AM

Limited Time Offer

25%

Off

Get Premium PMI-PBA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Terrilyn
3 months 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.
upvoted 0 times
Delmy
2 months ago
B) Create an interface analysis.
upvoted 0 times
...
Samuel
3 months ago
A) Create a fishbone diagram.
upvoted 0 times
...
...
Emile
3 months 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!
upvoted 0 times
...
Alease
3 months ago
I believe a Delphi estimation might provide us with a more accurate analysis of the root cause.
upvoted 0 times
...
Sherita
3 months ago
Functional decomposition, all the way! Break that problem down into bite-size pieces, easy peasy.
upvoted 0 times
...
Jeffrey
3 months ago
Interface analysis? Nah, that's not gonna cut it. We need to dig deeper, like a Delphi estimation or functional decomposition.
upvoted 0 times
Leila
2 months ago
True, let's use multiple methods to ensure we cover all angles in our analysis.
upvoted 0 times
...
Brent
2 months ago
I think a fishbone diagram could also be useful in identifying all possible causes.
upvoted 0 times
...
Jamie
3 months ago
I agree, a functional decomposition could also give us a better understanding of the issue.
upvoted 0 times
...
Tyisha
3 months ago
Let's go with a Delphi estimation, it might help us uncover the root cause.
upvoted 0 times
...
...
Curtis
3 months ago
Hmm, a fishbone diagram seems like the way to go. Gotta get to the root of that pesky software flaw!
upvoted 0 times
Elvera
2 months ago
D) Let's get to the bottom of this issue and find a solution.
upvoted 0 times
...
Lera
2 months ago
C) Once we have the diagram, we can start analyzing the different factors.
upvoted 0 times
...
Artie
2 months ago
B) I agree, it's a great tool for identifying root causes.
upvoted 0 times
...
Agustin
3 months ago
A) Create a fishbone diagram.
upvoted 0 times
...
...
Myrtie
4 months ago
I think creating a functional decomposition could also be helpful in understanding the discrepancy.
upvoted 0 times
...
Jamal
4 months ago
I agree with Fairy, a fishbone diagram can help us identify the causes of the software flaw.
upvoted 0 times
...
Fairy
4 months ago
I think we should create a fishbone diagram to analyze the root cause.
upvoted 0 times
...

Save Cancel