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?
You are correct because the lower priority requirements must be completed before the higher priority requirements can be done. In project management and business analysis, requirements prioritization is not only based on importance or business value but also on dependencies among the requirements. A higher priority requirement might depend on the functionality delivered by a lower priority requirement, necessitating that the lower priority requirement be implemented first to avoid bottlenecks and ensure the logical progression of the project.
A is the right answer
Could you please explain why A is the right answer? This seem like the higher requirements depends on the lower requirements, thus they have to be implemented. Page 82.
B cannot be correct, because order of priority means that requirements with higher priority should be implemented first, not the other way round
I agree the lower priority ones can't be done first, higher priorities are done first so I will choose A because priority is more on the business value
I think answer B is correct. We are talking about a requirement you moved in a higher position, to be implemented first. The lower requirement (the requirement you just moved to a higher position) should be done first. Question is a bit confusing cause it says that Ralph is disagree and you have to explain him that you move a lower requirement to an higher position, so that it can be done first. High requirements are done first and that is exactly what you have done by moving a low priority to high.
Answer is B since "Dependencies" is one of the factors that influence prioritization. BABOK v3 : Prioritize Requirements 5.3.4
"You are correct because the lower priority requirements must be completed before the higher priority requirements can be done. This is because in the given scenario, the low priority requirements are a dependency for high priority requirements. Ralph's approach is based on cost (i.e., difficulty in implementation) and not business value or importance. Also, even if Ralph's approach aligns with business value, the dependency factor matters more compared to business value or importance. It is because a high priority requirement with a high business value who is dependent on a low priority requirement with low business value needs to be implemented after the low priority requirement"
B is correct. The higher priority requirement depends on the lower one hence the lower one has to be implemented first
Option B Dependencies between requirements: Some capabilities may in and of themselves provide limited value to the organization, but need to be delivered in order to support other high-value requirements. Babok v2.- Page 126
Answer is B, but the funny thing here is that the question shows that the BAs cant understand each other. it is clear that higher req depends on the lower req so the lower should go first.
The higher priority requirement is dependent on the lower priority requirement.
Answer A - 5.3.2
Higher difficulty requirement is dependent on the lower difficulty one.
The ranking of the requirements based on their level of difficulty is fine, but you may also include a requirement's relationship to other requirements. If higher priority requirements cannot be completed until the lower priority requirements are done, then the requirements should be ordered as such for the order of implementation.