Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PMI Exam PMI-PBA Topic 1 Question 88 Discussion

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

Which of the following techniques is used to identify ambiguous or unverifiable requirements?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Nichelle
2 months ago
Hmm, I'm tempted to go with B) Fishbone analysis just because it sounds so fancy. Who doesn't love a good fishbone diagram, am I right?
upvoted 0 times
Erinn
22 days ago
Yeah, I think D) Team peer review could also be helpful in catching any unclear requirements.
upvoted 0 times
...
Ryann
1 months ago
I agree, a traceability matrix can really help track requirements and ensure they are clear.
upvoted 0 times
...
Cathrine
1 months ago
I think C) Traceability matrix is the best option for identifying ambiguous requirements.
upvoted 0 times
...
...
Micah
2 months ago
I'm going with C) Resource checklist. It's a simple but effective way to ensure all the necessary information is available to verify each requirement.
upvoted 0 times
Aliza
1 months ago
I would go with D) Team peer review. Having multiple team members review requirements can help identify any ambiguities.
upvoted 0 times
...
Tamie
2 months ago
I agree, C) Traceability matrix is a great tool for ensuring all requirements are clear and verifiable.
upvoted 0 times
...
Staci
2 months ago
I think C) Traceability matrix is the correct answer. It helps track requirements throughout the project.
upvoted 0 times
...
...
Mari
2 months ago
I'm not sure, but I think D) Traceability matrix could also be used to identify unverifiable requirements by tracing them back to their source.
upvoted 0 times
...
Earnestine
2 months ago
I agree with Harrison. Team peer review helps in identifying ambiguous requirements by getting multiple perspectives.
upvoted 0 times
...
Harrison
2 months ago
I think the answer is A) Team peer review.
upvoted 0 times
...
Lai
3 months ago
B) Fishbone analysis? Really? I'm not sure how that would help identify ambiguous requirements. Seems like a bit of a stretch.
upvoted 0 times
Lenna
2 months ago
D) Team peer review can also help in identifying ambiguous requirements by getting input from different team members.
upvoted 0 times
...
Matthew
2 months ago
C) Traceability matrix is actually the technique used to identify ambiguous or unverifiable requirements.
upvoted 0 times
...
Catherin
2 months ago
A) Fishbone analysis is a technique used to identify root causes of problems, not necessarily ambiguous requirements.
upvoted 0 times
...
...
Svetlana
3 months ago
D) Traceability matrix sounds like the right choice here. It helps trace requirements back to their sources, which can reveal any ambiguities.
upvoted 0 times
Benedict
2 months ago
C) Traceability matrix is the most thorough option for sure.
upvoted 0 times
...
Irma
2 months ago
D) Team peer review might catch some issues too.
upvoted 0 times
...
Rhea
2 months ago
A) I think Fishbone analysis could also help identify ambiguous requirements.
upvoted 0 times
...
Sylvie
2 months ago
C) Traceability matrix is definitely the way to go.
upvoted 0 times
...
...
Mabelle
3 months ago
I think the answer is A) Team peer review. It's a great way to identify ambiguous or unverifiable requirements by having the whole team review them together.
upvoted 0 times
Justa
2 months ago
I think Fishbone analysis could also help in identifying ambiguous requirements.
upvoted 0 times
...
Jerry
3 months ago
I agree, team peer review is a good way to catch those ambiguous requirements.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77