New Year Sale 2026! 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 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:

0/2000 characters
Submit Cancel
Domonique
2 months ago
Cost-benefit analysis seems off for this situation.
upvoted 0 times
...
Alesia
2 months ago
Totally agree, it helps gather existing info!
upvoted 0 times
...
Broderick
3 months ago
Wait, can you really do document analysis without the stakeholders?
upvoted 0 times
...
Gracia
3 months ago
I’m not so sure, brainstorming could spark new ideas.
upvoted 0 times
...
Brandon
3 months ago
Document analysis is a solid choice here.
upvoted 0 times
...
Shaunna
3 months ago
Document analysis sounds familiar, but I also think cost-benefit analysis could provide some insights. I just can't remember if it fits this scenario.
upvoted 0 times
...
Tijuana
4 months ago
I recall a practice question where benchmarking was used to compare processes, but I wonder if it’s really applicable without stakeholder input.
upvoted 0 times
...
Cyril
4 months ago
I'm not entirely sure, but I feel like brainstorming usually requires people to be present, so that might not work in this case.
upvoted 0 times
...
King
4 months ago
I think document analysis might be the best choice here since I remember it can help gather existing information without needing stakeholders right away.
upvoted 0 times
...
Nadine
4 months ago
Ah, this is a good one. I'd probably go with document analysis too. It's a good way to get the ball rolling while we wait for the stakeholders to be available. Feels like the most efficient approach.
upvoted 0 times
...
Jessenia
4 months ago
I think document analysis is the way to go here. It'll let me start gathering requirements without the stakeholders, and then I can follow up with them later. Seems like a solid strategy.
upvoted 0 times
...
Ronny
5 months ago
I'm a bit confused on this one. Brainstorming could be an option, but I'm not sure if that's the best approach when the stakeholders aren't involved. Maybe I should look into document analysis a bit more.
upvoted 0 times
...
Maxima
5 months ago
Hmm, this one's tricky. Since the stakeholders aren't available, I'd say document analysis might be the way to go. That could help me gather some initial requirements without them.
upvoted 0 times
...
Rikki
11 months ago
I think cost-benefit analysis could also be useful to prioritize requirements while waiting for stakeholders.
upvoted 0 times
...
Chantay
11 months ago
I prefer brainstorming, it can help generate new ideas even without stakeholders present.
upvoted 0 times
...
Mica
11 months ago
I agree with Viola, document analysis can help us gather information from existing documents.
upvoted 0 times
...
Paola
11 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
11 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
11 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
10 months 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
10 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
11 months ago
A: Let's try document analysis to gather information while we wait for the stakeholders.
upvoted 0 times
...
...
Viola
11 months ago
I think we should use document analysis.
upvoted 0 times
...
Dorcas
11 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
11 months ago
Cost-benefit analysis might be useful to prioritize requirements once the stakeholders are available.
upvoted 0 times
...
Marjory
11 months ago
Brainstorming could also be helpful to generate ideas while waiting for the stakeholders.
upvoted 0 times
...
Cathrine
11 months ago
Document analysis is a good choice. We can gather a lot of information from existing documents.
upvoted 0 times
...
...

Save Cancel