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 6 Question 77 Discussion

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

A project team has 120 days to deliver a solution, but the stakeholders have too many requirements for the delivery window. What requirements prioritization technique should be used to determine which requirements will be delivered?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Larue at May 09, 2024, 10:31 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
Jolanda
2 months ago
Not sure if MoSCoW will really cover all the stakeholder needs.
upvoted 0 times
...
Gladys
2 months ago
I think multivoting could work too, but MoSCoW is more structured.
upvoted 0 times
...
Eun
3 months ago
Surprised that budget analysis isn't even an option here!
upvoted 0 times
...
Brock
3 months ago
Time-boxing seems too limiting for this situation.
upvoted 0 times
...
Ora
3 months ago
MoSCoW is the best choice for prioritizing requirements!
upvoted 0 times
...
Dortha
3 months ago
Budget analysis seems off for this scenario; it doesn't really help with prioritizing requirements directly. I lean towards MoSCoW as well.
upvoted 0 times
...
Rosann
4 months ago
I practiced a similar question, and I think time-boxing is more about managing tasks within a timeframe rather than prioritizing requirements.
upvoted 0 times
...
Phil
4 months ago
I'm not entirely sure, but I feel like multivoting could work too. It allows the team to gauge what’s most important to everyone.
upvoted 0 times
...
Rupert
4 months ago
I remember studying prioritization techniques, and I think MoSCoW might be the right choice since it helps categorize requirements based on urgency.
upvoted 0 times
...
Deeanna
4 months ago
I feel pretty confident that MoSCoW is the way to go here. It's a straightforward method for categorizing requirements based on their importance, which is exactly what we need to do given the limited timeline.
upvoted 0 times
...
Isadora
4 months ago
Budget analysis? That doesn't seem relevant to prioritizing requirements. I'm leaning towards MoSCoW since it's a well-known technique for balancing stakeholder needs with delivery constraints.
upvoted 0 times
...
Melvin
5 months ago
Hmm, I'm not sure about this one. There are a few different techniques we could use, like multivoting or time-boxing. I'll need to think through the pros and cons of each before deciding.
upvoted 0 times
...
Johnetta
5 months ago
This seems like a classic requirements prioritization problem. I think MoSCoW would be the best approach here to quickly identify the must-have, should-have, could-have, and won't-have requirements given the tight timeline.
upvoted 0 times
...
Lavera
5 months ago
I've got a good feeling about this one. I think I know the answer, but I'll double-check my notes just to be sure.
upvoted 0 times
...
Rusty
5 months ago
I think the Anti-DDoS Service Pro would be the best choice for maintaining a high availability under DDoS attacks, but I'm not entirely sure why the others wouldn't be sufficient.
upvoted 0 times
...
Casie
10 months ago
Gotta love those stakeholders and their endless requirements! B) MoSCoW is definitely the way to go to keep this project from turning into a dumpster fire.
upvoted 0 times
Shelton
8 months ago
True, but MoSCoW is more structured and efficient in this situation.
upvoted 0 times
...
Dorothy
8 months ago
Multivoting could also be useful to get everyone's input on priorities.
upvoted 0 times
...
Argelia
9 months ago
I agree, it helps to focus on what must be delivered first.
upvoted 0 times
...
Glenna
10 months ago
MoSCoW is a great technique to prioritize requirements.
upvoted 0 times
...
...
Erick
10 months ago
Time-boxing? Really? C) Time-boxing is more about managing the schedule, not prioritizing requirements. B) MoSCoW is the way to go here.
upvoted 0 times
Alex
9 months ago
B) MoSCoW is the way to go here.
upvoted 0 times
...
Nelida
9 months ago
Time-boxing? Really? C) Time-boxing is more about managing the schedule, not prioritizing requirements.
upvoted 0 times
...
...
Tawna
11 months ago
I'm not sure about MoSCoW, I think Time-boxing could also be a good option to manage the requirements within the delivery window.
upvoted 0 times
...
Adell
11 months ago
A) Multivoting could work too, but MoSCoW is probably a safer bet in this scenario. It's more structured and provides clearer guidance.
upvoted 0 times
Moon
9 months ago
D) Budget analysis may not be as relevant for prioritizing requirements in this case.
upvoted 0 times
...
Jerry
9 months ago
C) Time-boxing could also be useful to ensure requirements are delivered within the 120-day window.
upvoted 0 times
...
Gilberto
10 months ago
B) I agree, MoSCoW helps prioritize requirements based on their importance.
upvoted 0 times
...
Dominque
10 months ago
A) Multivoting could work too, but MoSCoW is probably a safer bet in this scenario.
upvoted 0 times
...
...
Gerry
11 months ago
I'd go with B) MoSCoW. It's a classic requirements prioritization technique that works great when you have too many requirements and not enough time.
upvoted 0 times
...
Elly
11 months ago
B) MoSCoW seems like the obvious choice here. It allows the team to prioritize the must-haves and negotiate the nice-to-haves with the stakeholders.
upvoted 0 times
...
Teresita
11 months ago
I agree with Arlette, MoSCoW will help us identify the must-haves for the project delivery.
upvoted 0 times
...
Arlette
11 months ago
I think we should use the MoSCoW technique to prioritize the requirements.
upvoted 0 times
...

Save Cancel