volume_mute

During elicitation, a BA discovers a requirement that is very high value but also carries a significant technical risk that might jeopardize the entire project. What is the best way to handle this during prioritization?

publish date: 2026/03/06 07:59:31.064628 UTC

volume_mute

Involve technical experts and stakeholders to balance value against risk

Prioritize it as low to avoid dealing with the risk until the end

Discard the requirement immediately to save the project

Mark it as 'Must Have' and ignore the technical concerns

Involve technical experts and stakeholders to balance value against risk

Prioritization is a collaborative effort to ensure high-value/high-risk items are understood and managed early.

go-math-science.com