PMI-PBA Exam - Topic 5 Question 74 Discussion

Actual exam question for PMI's PMI-PBA exam

Question #: 74
Topic #: 5

An insurance company embarks on a project to replace its current enrollment and billing software application, which will no longer be supported by the end of the calendar year. The new enrollment and billing application must be implemented before the current vendor contract ends. The business analyst gathers the initial requirements for the new enrollment and billing application. Based on the large

volume of requirements, the business analyst realizes that the requirements will need to be prioritized.

Which requirements prioritization method should the business analyst use for this project?

ATime-boxing

BWeighted ranking

CMoSCoW

DRisk analysis

Show Suggested Answer

Suggested Answer: B

by Whitley at Apr 10, 2024, 11:59 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Rene

3 months ago

Wait, risk analysis? Isn’t that more for assessing threats than prioritizing requirements?

upvoted 0 times

...

Laine

3 months ago

Definitely MoSCoW! Prioritizing like that makes total sense.

upvoted 0 times

...

Jaclyn

3 months ago

Time-boxing? Really? That doesn't sound right for this situation.

upvoted 0 times

...

Leonora

4 months ago

Weighted ranking seems more effective for complex projects.

upvoted 0 times

...

Barabara

4 months ago

I think MoSCoW is the best choice here.

upvoted 0 times

...

Cordie

4 months ago

Risk analysis sounds relevant, but I’m not sure if it’s the best method for prioritizing requirements specifically. I might need to review that section again.

upvoted 0 times

...

Monte

4 months ago

I feel like time-boxing is more about managing tasks rather than prioritizing requirements. I’m leaning towards MoSCoW.

upvoted 0 times

...

Truman

4 months ago

I'm not entirely sure, but I think weighted ranking could help quantify the importance of each requirement. It might be useful here.

upvoted 0 times

...

Ty

5 months ago

I remember studying the MoSCoW method, and it seems like a good fit for prioritizing requirements based on urgency and importance.

upvoted 0 times

...

Dean

5 months ago

I'm a little confused by the options presented. Time-boxing and risk analysis don't seem directly relevant to prioritizing requirements. I think I'll need to carefully consider the differences between weighted ranking and MoSCoW to determine the best approach for this scenario.

upvoted 0 times

...

Hassie

5 months ago

Okay, I've got this. Based on the details provided, the business analyst should use the MoSCoW method to prioritize the requirements. This method allows for clear categorization of requirements as Must have, Should have, Could have, or Won't have, which seems well-suited for this project's tight timeline.

upvoted 0 times

...

Raina

5 months ago

Hmm, I'm a bit unsure about this one. There are a few different prioritization methods mentioned, and I'm not entirely sure which one would be most appropriate for this scenario. I may need to review the differences between them to make a more informed decision.

upvoted 0 times

...

Rebeca

5 months ago

This seems like a straightforward requirements prioritization question. I think the MoSCoW method would be the best approach here, as it aligns with the need to prioritize the large volume of requirements before the deadline.

upvoted 0 times

...

Lizbeth

5 months ago

I'm a little confused by the options here. "Bearer Token" and "RestAuth" sound like authentication methods, but I'm not familiar with them in the context of Cisco UCS Director. I'll have to do a quick review of the documentation to make sure I select the correct answer.

upvoted 0 times

...

Thea

5 months ago

Hmm, I'm a little stumped on this one. I know IBM has a lot of database products, but I'm not super familiar with the specifics of their cloud migration capabilities. I'll have to make an educated guess on this one.

upvoted 0 times

...

Lizette

5 months ago

Hmm, I'm a bit unsure about this one. The scenario talks about a firewall being placed, so I'm not sure if that's considered accepting, avoiding, transferring, or mitigating the risk.

upvoted 0 times

...

My

10 months ago

I heard the insurance company is using a magic 8-ball to prioritize the requirements. It's the latest in cutting-edge project management techniques!

upvoted 0 times

...

Jolanda

10 months ago

Time-boxing? More like time-crunch! This is no time for experimenting with fancy prioritization methods. MoSCoW is the way to go, hands down.

upvoted 0 times

Annice

8 months ago

Exactly, MoSCoW will ensure we deliver the most important requirements first and meet the project deadline.

upvoted 0 times

...

Sage

8 months ago

I agree, with the tight deadline, we need a method that helps us focus on what is Must have, Should have, Could have, and Won't have.

upvoted 0 times

...

Minna

9 months ago

Weighted ranking might take too long, MoSCoW will help us focus on what's essential.

upvoted 0 times

...

Derrick

9 months ago

MoSCoW is definitely the way to go for prioritizing requirements in this project.

upvoted 0 times

...

Adelaide

9 months ago

I agree, with the tight deadline, we need a method that can quickly identify the must-haves.

upvoted 0 times

...

Simona

9 months ago

MoSCoW is definitely the way to go for prioritizing requirements in this project.

upvoted 0 times

...

Veda

10 months ago

Risk analysis? Really? I don't think we have time to analyze every potential risk when the clock is ticking on the current vendor contract.

upvoted 0 times

Ardella

9 months ago

C) MoSCoW

upvoted 0 times

...

Alex

9 months ago

C) MoSCoW

upvoted 0 times

...

Destiny

9 months ago

B) Weighted ranking

upvoted 0 times

...

Miesha

9 months ago

B) Weighted ranking

upvoted 0 times

...

Otis

9 months ago

A) Time-boxing

upvoted 0 times

...

Jarvis

10 months ago

A) Time-boxing

upvoted 0 times

...

Verda

10 months ago

Weighted ranking might be a bit overkill for this project. We need something straightforward that can get the job done quickly.

upvoted 0 times

...

Maddie

11 months ago

MoSCoW seems like the way to go here. With a tight timeline, we need to focus on the Must-haves first and then tackle the Should-haves and Could-haves as time permits.

upvoted 0 times