The best answer is B because agile teams should use frequent feedback, customer data, and learning to adapt priorities. The problem is that teams are continuing to invest in low-adoption features because feedback is reviewed too late. Integrating usage analytics into prioritization creates a shorter feedback loop and supports value-based decision-making.

Option A improves review frequency but still keeps decisions at an executive review level rather than embedding feedback into the team’s prioritization process. Option C shifts decision-making to regional managers, but agile prioritization should still consider product value, customer outcomes, and team learning. Option D focuses on output rather than outcome; delivering more features does not necessarily reduce churn or improve value.

PMI-ACP topics emphasize maximizing value, adapting to feedback, engaging stakeholders early, and using empirical information to improve future increments.

=========