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

PMI-PBA Exam - Topic 6 Question 77 Discussion

Posted by Larue on May 09, 2024 at 10:31 PM

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?

Suggested Answer: C

Get Premium PMI-PBA Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
33 comments · newest first
JO
Jolanda 11 months ago
Not sure if MoSCoW will really cover all the stakeholder needs.
GL
Gladys 11 months ago
I think multivoting could work too, but MoSCoW is more structured.
EU
Eun 11 months ago
Surprised that budget analysis isn't even an option here!
BR
Brock 11 months ago
Time-boxing seems too limiting for this situation.
OR
Ora 11 months ago
MoSCoW is the best choice for prioritizing requirements!
DO
Dortha 12 months ago
Budget analysis seems off for this scenario; it doesn't really help with prioritizing requirements directly. I lean towards MoSCoW as well.
RO
Rosann 12 months ago
I practiced a similar question, and I think time-boxing is more about managing tasks within a timeframe rather than prioritizing requirements.
PH
Phil 1 year 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.
RU
Rupert 1 year ago
I remember studying prioritization techniques, and I think MoSCoW might be the right choice since it helps categorize requirements based on urgency.
DE
Deeanna 1 year 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.
IS
Isadora 1 year 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.
ME
Melvin 1 year 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.
JO
Johnetta 1 year 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.
LA
Lavera 1 year 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.
RU
Rusty 1 year 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.
CA
Casie 2 years 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.
SH
Shelton 1 year ago
↳ replying to Casie
True, but MoSCoW is more structured and efficient in this situation.
DO
Dorothy 1 year ago
↳ replying to Casie
Multivoting could also be useful to get everyone's input on priorities.
AR
Argelia 1 year ago
↳ replying to Casie
I agree, it helps to focus on what must be delivered first.
GL
Glenna 2 years ago
↳ replying to Casie
MoSCoW is a great technique to prioritize requirements.
ER
Erick 2 years ago
Time-boxing? Really? C) Time-boxing is more about managing the schedule, not prioritizing requirements. B) MoSCoW is the way to go here.
AL
Alex 1 year ago
↳ replying to Erick
B) MoSCoW is the way to go here.
NE
Nelida 1 year ago
↳ replying to Erick
Time-boxing? Really? C) Time-boxing is more about managing the schedule, not prioritizing requirements.
TA
Tawna 2 years 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.
AD
Adell 2 years ago
A) Multivoting could work too, but MoSCoW is probably a safer bet in this scenario. It's more structured and provides clearer guidance.
MO
Moon 1 year ago
↳ replying to Adell
D) Budget analysis may not be as relevant for prioritizing requirements in this case.
JE
Jerry 1 year ago
↳ replying to Adell
C) Time-boxing could also be useful to ensure requirements are delivered within the 120-day window.
GI
Gilberto 2 years ago
↳ replying to Adell
B) I agree, MoSCoW helps prioritize requirements based on their importance.
DO
Dominque 2 years ago
↳ replying to Adell
A) Multivoting could work too, but MoSCoW is probably a safer bet in this scenario.
GE
Gerry 2 years 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.
EL
Elly 2 years 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.
TE
Teresita 2 years ago
I agree with Arlette, MoSCoW will help us identify the must-haves for the project delivery.
AR
Arlette 2 years ago
I think we should use the MoSCoW technique to prioritize the requirements.
0/2000 characters

Save Cancel