Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PMI Exam PMI-PBA Topic 5 Question 74 Discussion

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

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

My
1 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
1 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
Sage
6 days 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
8 days ago
Weighted ranking might take too long, MoSCoW will help us focus on what's essential.
upvoted 0 times
...
Derrick
16 days ago
MoSCoW is definitely the way to go for prioritizing requirements in this project.
upvoted 0 times
...
Adelaide
1 months ago
I agree, with the tight deadline, we need a method that can quickly identify the must-haves.
upvoted 0 times
...
Simona
1 months ago
MoSCoW is definitely the way to go for prioritizing requirements in this project.
upvoted 0 times
...
...
Veda
2 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
17 days ago
C) MoSCoW
upvoted 0 times
...
Alex
23 days ago
C) MoSCoW
upvoted 0 times
...
Destiny
23 days ago
B) Weighted ranking
upvoted 0 times
...
Miesha
24 days ago
B) Weighted ranking
upvoted 0 times
...
Otis
1 months ago
A) Time-boxing
upvoted 0 times
...
Jarvis
1 months ago
A) Time-boxing
upvoted 0 times
...
...
Verda
2 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
2 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
Stephaine
1 months ago
Yes, we need to ensure that we deliver the essential features before the deadline.
upvoted 0 times
...
Jarvis
2 months ago
I agree, MoSCoW prioritization method will help us focus on the most critical requirements first.
upvoted 0 times
...
...
Nobuko
2 months ago
I prefer using weighted ranking because it allows us to assign importance to each requirement based on its impact.
upvoted 0 times
...
Lavonne
2 months ago
I agree with Lezlie, MoSCoW is a good method to use in this situation.
upvoted 0 times
...
Lezlie
3 months ago
I think we should use the MoSCoW method for prioritizing 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