Kendra is the business analyst for her organization. She's working with the project manager and the project sponsor to discuss the current requirements. Kendra believes it's important for the project manager to first implement the requirements with the highest amount of risks. Is this a good idea?

BABOK recommends risk-based prioritisation: requirements with the greatest technical or business risk should be addressed as early as feasible so there is time to resolve issues or, if necessary, cancel the endeavour before major expenditure. Therefore Kendra’s position is sound and option D, which states the risks are tackled as soon as possible in the schedule, best reflects accepted practice.

A. Implementing low-risk items first delays discovery of high-risk problems, increasing overall project exposure.
B. Although early failure limits sunk cost, the option does not stress proactive scheduling; D captures both cost and schedule intent more precisely.
C. Leaving high-risk requirements until last heightens probability of late-stage failure and rework.

1. IIBA. BABOK v3

§5.3 Prioritize Requirements – “Risk”

p. 123.

2. Massachusetts Institute of Technology

Course 15.053 “Optimization Methods”

Risk-driven development lecture notes

slide 11 (emphasise addressing greatest risks early).