One of the processes within requirements analysis is to prioritize requirements.
As a business analyst why would you ever want to prioritize requirements?
One of the processes within requirements analysis is to prioritize requirements.
As a business analyst why would you ever want to prioritize requirements?
One of the key reasons to prioritize requirements as a business analyst is to determine which requirements are most critical so that the analysis and implementation efforts can be focused on those. Prioritization helps to ensure that the most important and valuable requirements are addressed first, optimizing the allocation of resources and efforts to deliver the most impactful results efficiently.
I think C...Anyone out there??
BABOK v3 p87 Priority can refer to the relative value of a requirement, or to the sequence in which it will be implemented. P
Best answer is C
C. You may need to determine which requirements are most critical so the analysis and implementation efforts focus on the most critical requirements.
The other answers focus on cost, schedule and risk, which are all part of factors that influence prioritization, along benefit, dependencies, stability and regulatory or policy compliance. "Prioritization is an assessment of relative value. Each stakeholder may value something different."(BABOK V3 pg 89) Since we can not assume what is prioritized from a stakeholder perspective, the answer is C.
C Prioritization is an ongoing process, with priorities changing as the context changes.
According to BABOK