CBAP · Question #262
You are the business analyst for your organization and are working with Ralph who is also a business analyst at your company. You have moved one of the requirements higher in the prioritization of…
The correct answer is B. You are correct because the lower priority requirements must be completed before the higher. Requirements prioritization can be driven by dependencies, meaning a lower-priority requirement may legitimately be scheduled first if it is a prerequisite for higher-priority ones.
Question
You are the business analyst for your organization and are working with Ralph who is also a business analyst at your company. You have moved one of the requirements higher in the prioritization of the requirements because it is needed to be implemented before some of the more important requirements are done. Ralph disagrees with your placement of the requirement because you are to rank the requirements based on their level of difficulty. Who is correct and why?
Options
- ARalph is correct because the requirements are always to be ranked by importance or business
- BYou are correct because the lower priority requirements must be completed before the higher
- CYou are correct because you are the senior business analyst.
- DRalph is correct because the sequence of requirements is actually done with the project
How the community answered
(20 responses)- A15% (3)
- B70% (14)
- C10% (2)
- D5% (1)
Why each option
Requirements prioritization can be driven by dependencies, meaning a lower-priority requirement may legitimately be scheduled first if it is a prerequisite for higher-priority ones.
Requirements are not always ranked exclusively by importance or business value - dependency and sequencing constraints are equally valid prioritization criteria.
Dependency-based prioritization is a recognized technique in which the implementation sequence is determined by logical or technical prerequisites rather than business value alone. When a lower-priority requirement must be completed before a higher-priority requirement can be built or tested, elevating it in the schedule is correct practice. This approach ensures that implementation order reflects real-world constraints, not just ranked importance.
Seniority does not determine the correctness of a prioritization decision; the technical or logical justification for the ordering is what matters.
Sequencing requirements based on project management concerns conflates project scheduling with requirements prioritization, which are separate activities.
Concept tested: Dependency-based requirements prioritization sequencing
Topics
Community Discussion
No community discussion yet for this question.