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 7 Question 71 Discussion

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

A business analyst is documenting the acceptance criteria to suppon a minor modification in a user portal The analyst submits the criteria for review, but it is deemed incomplete and returned.

What could have caused the documentation to be returned?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Kristofer at Feb 08, 2024, 12:46 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Detra
8 months ago
I beliDetra the analyst failed to gather any baseline information which could have caused the documentation to be returned.
upvoted 0 times
...
Franchesca
8 months ago
But wouldn't using user stories help in detailing the requirements better?
upvoted 0 times
...
Felicitas
8 months ago
I think the analyst should have used user stories as a requirements document tool.
upvoted 0 times
...
Kristin
8 months ago
I agree with Franchesca. Without the scope document, the acceptance criteria could be incomplete.
upvoted 0 times
...
Franchesca
8 months ago
I think the documentation was returned because the analyst did not include the scope document.
upvoted 0 times
...
Clemencia
8 months ago
Yeah, it's important to have all the necessary information in the acceptance criteria.
upvoted 0 times
...
Diane
8 months ago
That could be the reason why it was returned, user stories may not be enough.
upvoted 0 times
...
Vincenza
8 months ago
I heard that the analyst used user stories as a requirements document.
upvoted 0 times
...
Clemencia
9 months ago
Or maybe they didn't perform forward and backwards traceability.
upvoted 0 times
...
Diane
10 months ago
Maybe the analyst forgot to include the scope document.
upvoted 0 times
...
Clemencia
10 months ago
I think the documentation was returned because it was incomplete.
upvoted 0 times
...
Elvis
11 months ago
Haha, good one! Yeah, I could see that happening. The analyst probably thought they were being innovative, but the old-school review team wasn't having it.
upvoted 0 times
...
Zita
11 months ago
Hey, maybe the analyst got a little too creative and tried to use user stories instead of a traditional requirements doc. That would definitely not fly with the reviewers!
upvoted 0 times
...
Kasandra
11 months ago
I agree, the question is a bit ambiguous. The analyst could have failed to include key details like the specific scope of the modification or the user requirements. That would definitely cause the documentation to be returned.
upvoted 0 times
Geraldine
10 months ago
Traceability is important to ensure all requirements are properly documented.
upvoted 0 times
...
Josephine
10 months ago
A) The analyst performed forward and backwards traceability.
upvoted 0 times
...
Vallie
10 months ago
Without the baseline information, it would be difficult to assess the impact of the modification.
upvoted 0 times
...
Gerald
10 months ago
B) The analyst failed to gather any baseline information.
upvoted 0 times
...
Kimbery
10 months ago
That could definitely be a crucial missing piece in the documentation.
upvoted 0 times
...
Gladis
10 months ago
C) The analyst did not include the scope document in the acceptance criteria paperwork.
upvoted 0 times
...
Luisa
10 months ago
I'm not sure if that was the reason for the documentation being returned.
upvoted 0 times
...
Daren
10 months ago
A) The analyst performed forward and backwards traceability.
upvoted 0 times
...
...
Benedict
11 months ago
This seems like a straightforward question, but I'm a little worried about the wording. The acceptance criteria should be clear and comprehensive, so I'm not sure why it would be returned as incomplete.
upvoted 0 times
...

Save Cancel