What is a prudent response when stakeholder votes do not address the root cause?

• A. Ignore the root cause and proceed
• B. Use votes to determine the entire roadmap
• C. Align decisions with the identified root cause and communicate expectations
• D. Stop development entirely

Answer: (C)

When stakeholder votes don’t address the underlying problem, the focus should be on the root cause and what it means for delivering value. The Product Owner bases decisions on evidence and understanding of the root cause, then aligns the backlog and roadmap to fix that problem. This often means prioritizing work that directly addresses the root cause, refining acceptance criteria to reflect the needed outcomes, and communicating clearly to stakeholders what will change and why. By doing this, you maintain a coherent plan that targets real value, while keeping everyone informed about expectations and how success will be measured.

This approach also supports transparency and collaboration in scrum: you examine data, validate the root cause with stakeholders, and adapt the backlog and product goals accordingly. Ignoring the root cause or letting votes dictate the entire roadmap can lead to wasted effort or misaligned priorities, and stopping development halts progress. The prudent path is to align decisions with the root cause and communicate the plan and expectations clearly.