MENU
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?
Suggested Answer: B
Get Premium PMI-PBA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
38 comments · newest first
RE
Rene
11 months ago
Wait, risk analysis? Isn’t that more for assessing threats than prioritizing requirements?
LA
Laine
11 months ago
Definitely MoSCoW! Prioritizing like that makes total sense.
JA
Jaclyn
12 months ago
Time-boxing? Really? That doesn't sound right for this situation.
LE
Leonora
12 months ago
Weighted ranking seems more effective for complex projects.
BA
Barabara
1 year ago
I think MoSCoW is the best choice here.
CO
Cordie
1 year 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.
MO
Monte
1 year ago
I feel like time-boxing is more about managing tasks rather than prioritizing requirements. I’m leaning towards MoSCoW.
TR
Truman
1 year ago
I'm not entirely sure, but I think weighted ranking could help quantify the importance of each requirement. It might be useful here.
TY
Ty
1 year ago
I remember studying the MoSCoW method, and it seems like a good fit for prioritizing requirements based on urgency and importance.
DE
Dean
1 year 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.
HA
Hassie
1 year 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.
RA
Raina
1 year 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.
RE
Rebeca
1 year 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.
LI
Lizbeth
1 year 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.
TH
Thea
1 year 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.
LI
Lizette
1 year 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.
MY
My
1 year 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!
JO
Jolanda
1 year 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.
AN
Annice
1 year ago
Exactly, MoSCoW will ensure we deliver the most important requirements first and meet the project deadline.
SA
Sage
1 year 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.
MI
Minna
1 year ago
Weighted ranking might take too long, MoSCoW will help us focus on what's essential.
DE
Derrick
1 year ago
MoSCoW is definitely the way to go for prioritizing requirements in this project.
AD
Adelaide
1 year ago
I agree, with the tight deadline, we need a method that can quickly identify the must-haves.
SI
Simona
1 year ago
MoSCoW is definitely the way to go for prioritizing requirements in this project.
VE
Veda
2 years 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.
AR
Ardella
1 year ago
C) MoSCoW
AL
Alex
1 year ago
C) MoSCoW
DE
Destiny
1 year ago
B) Weighted ranking
MI
Miesha
1 year ago
B) Weighted ranking
OT
Otis
1 year ago
A) Time-boxing
JA
Jarvis
1 year ago
A) Time-boxing
VE
Verda
2 years ago
Weighted ranking might be a bit overkill for this project. We need something straightforward that can get the job done quickly.
MA
Maddie
2 years 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.
ST
Stephaine
2 years ago
Yes, we need to ensure that we deliver the essential features before the deadline.
JA
Jarvis
2 years ago
I agree, MoSCoW prioritization method will help us focus on the most critical requirements first.
NO
Nobuko
2 years ago
I prefer using weighted ranking because it allows us to assign importance to each requirement based on its impact.
LA
Lavonne
2 years ago
I agree with Lezlie, MoSCoW is a good method to use in this situation.
LE
Lezlie
2 years ago
I think we should use the MoSCoW method for prioritizing requirements.