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-PBA Exam - Topic 7 Question 71 Discussion

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?
B) The analyst failed to gather any baseline information.
A) The analyst performed forward and backwards traceability.
C) The analyst did not include the scope document in the acceptance criteria paperwork.
D) The analyst utilized user stories as a requirements document tool.

PMI-PBA Exam - 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:

0/2000 characters
Submit Cancel
Katlyn
6 months ago
User stories alone aren't enough for acceptance criteria.
upvoted 0 times
...
Dong
6 months ago
Wait, how could they not gather baseline info? That’s basic!
upvoted 0 times
...
Amie
7 months ago
I think including the scope document is a must.
upvoted 0 times
...
Nikita
7 months ago
Totally agree, baseline info is crucial!
upvoted 0 times
...
Stefanie
7 months ago
Sounds like they missed some key info.
upvoted 0 times
...
Gregoria
7 months ago
I vaguely recall that user stories might not be enough on their own for acceptance criteria. If that’s the case, then option D could be a reason for the return.
upvoted 0 times
...
Mayra
8 months ago
I feel like we practiced a question similar to this where traceability was mentioned. If the analyst did that correctly, I don’t see how it could be the issue.
upvoted 0 times
...
Ashley
8 months ago
I’m not sure, but I think including the scope document is crucial for acceptance criteria. If it wasn’t there, that might be why it got returned.
upvoted 0 times
...
Beckie
8 months ago
I remember we discussed how important it is to gather baseline information. If that was missing, it could definitely lead to the documentation being incomplete.
upvoted 0 times
...
Alita
8 months ago
Okay, let me see here. I think the key is to focus on what the acceptance criteria documentation should include. The options mention things like traceability, baseline information, and scope documents - those sound like important elements that may have been missing. I'll need to weigh the options to find the best answer.
upvoted 0 times
...
Cordelia
8 months ago
Hmm, I'm a bit unsure about this one. The question is asking what could have caused the documentation to be returned, but the options don't seem to directly address that. I'll need to think through each option carefully to determine the most likely reason.
upvoted 0 times
...
Corinne
8 months ago
This seems like a straightforward question about acceptance criteria documentation. I'll need to carefully review the options and think about what key elements might be missing from the analyst's submission.
upvoted 0 times
...
Veronika
8 months ago
This is a tricky one. I'm not entirely sure what the "acceptance criteria" refers to in this context. Is it just the requirements documentation, or something more specific? I'll need to make sure I understand the terminology before I can confidently select an answer.
upvoted 0 times
...
Melvin
8 months ago
This is a tricky one. I know the internal auditor is supposed to be independent, but I'm not sure if that means the Board or the shareholders would be responsible for the appointment. I'll have to weigh the options carefully.
upvoted 0 times
...
Tijuana
8 months ago
Okay, I got this. The key is to identify the fastest scaling mode, which is ECI at 30 seconds. So the statement must be true. Easy peasy!
upvoted 0 times
...
Detra
2 years ago
I beliDetra the analyst failed to gather any baseline information which could have caused the documentation to be returned.
upvoted 0 times
...
Franchesca
2 years ago
But wouldn't using user stories help in detailing the requirements better?
upvoted 0 times
...
Felicitas
2 years ago
I think the analyst should have used user stories as a requirements document tool.
upvoted 0 times
...
Kristin
2 years ago
I agree with Franchesca. Without the scope document, the acceptance criteria could be incomplete.
upvoted 0 times
...
Franchesca
2 years ago
I think the documentation was returned because the analyst did not include the scope document.
upvoted 0 times
...
Clemencia
2 years ago
Yeah, it's important to have all the necessary information in the acceptance criteria.
upvoted 0 times
...
Diane
2 years ago
That could be the reason why it was returned, user stories may not be enough.
upvoted 0 times
...
Vincenza
2 years ago
I heard that the analyst used user stories as a requirements document.
upvoted 0 times
...
Clemencia
2 years ago
Or maybe they didn't perform forward and backwards traceability.
upvoted 0 times
...
Diane
2 years ago
Maybe the analyst forgot to include the scope document.
upvoted 0 times
...
Clemencia
2 years ago
I think the documentation was returned because it was incomplete.
upvoted 0 times
...
Elvis
2 years 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
2 years 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
2 years 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
2 years ago
Traceability is important to ensure all requirements are properly documented.
upvoted 0 times
...
Josephine
2 years ago
A) The analyst performed forward and backwards traceability.
upvoted 0 times
...
Vallie
2 years ago
Without the baseline information, it would be difficult to assess the impact of the modification.
upvoted 0 times
...
Gerald
2 years ago
B) The analyst failed to gather any baseline information.
upvoted 0 times
...
Kimbery
2 years ago
That could definitely be a crucial missing piece in the documentation.
upvoted 0 times
...
Gladis
2 years ago
C) The analyst did not include the scope document in the acceptance criteria paperwork.
upvoted 0 times
...
Luisa
2 years ago
I'm not sure if that was the reason for the documentation being returned.
upvoted 0 times
...
Daren
2 years ago
A) The analyst performed forward and backwards traceability.
upvoted 0 times
...
...
Benedict
2 years 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