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 3 Question 99 Discussion

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

A business analyst is ready to begin requirements elicitation; however, stakeholders are not available to participate for another two weeks. Which elicitation technique should the business analyst use during this time?

Show Suggested Answer Hide Answer
Suggested Answer: D

The business analyst should use document analysis as an elicitation technique during this time. Document analysis is a technique that involves reviewing and analyzing existing documents, such as policies, procedures, standards, reports, or contracts, to elicit information about the business needs, requirements, or solution options. Document analysis is useful when the stakeholders are not available to participate, or when the business analyst needs to gain background knowledge or context before engaging with the stakeholders.Document analysis can also help to identify gaps, issues, or assumptions that need to be clarified or validated with the stakeholders later.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 12; Business Analysis for Practitioners: A Practice Guide2, page 51.


by Kirby at Mar 19, 2025, 05:40 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Rikki
1 months ago
I think cost-benefit analysis could also be useful to prioritize requirements while waiting for stakeholders.
upvoted 0 times
...
Chantay
1 months ago
I prefer brainstorming, it can help generate new ideas even without stakeholders present.
upvoted 0 times
...
Mica
1 months ago
I agree with Viola, document analysis can help us gather information from existing documents.
upvoted 0 times
...
Paola
2 months ago
I'd go with document analysis. It's the safest option, and we can use it to get a head start on the requirements. Plus, it's a great way to procrastinate if you ask me!
upvoted 0 times
...
Aja
2 months ago
Benchmarking sounds like a good idea, but I'm not sure how relevant it would be without the stakeholders. Maybe we could do some research and then get their input when they're available.
upvoted 0 times
...
Tammy
2 months ago
Brainstorming could be interesting, but I'm not sure it's the best fit if the stakeholders aren't around. Maybe we could do some solo brainstorming and then have them review it later.
upvoted 0 times
Lai
28 days ago
A: Agreed, it will help us make the most of the time before we can engage with the stakeholders directly.
upvoted 0 times
...
Merlyn
1 months ago
B: That sounds like a good idea. We can review the documents and prepare questions for when the stakeholders are available.
upvoted 0 times
...
Raymon
1 months ago
A: Let's try document analysis to gather information while we wait for the stakeholders.
upvoted 0 times
...
...
Viola
2 months ago
I think we should use document analysis.
upvoted 0 times
...
Dorcas
2 months ago
I think document analysis is the way to go. The stakeholders aren't available, so we need to dig into the existing documentation to get started.
upvoted 0 times
Venita
2 months ago
Cost-benefit analysis might be useful to prioritize requirements once the stakeholders are available.
upvoted 0 times
...
Marjory
2 months ago
Brainstorming could also be helpful to generate ideas while waiting for the stakeholders.
upvoted 0 times
...
Cathrine
2 months ago
Document analysis is a good choice. We can gather a lot of information from existing documents.
upvoted 0 times
...
...

Save Cancel