The correct answer is C - The users can help the team understand if the feature adds value, avoiding the risk of building the wrong product.
Prototyping in agile serves as a lightweight modeling technique that supports discovery and stakeholder validation. It helps clarify uncertain requirements, encourages collaboration, and ensures that the solution being developed meets user needs and delivers value.
From the PMI Agile Practice Guide:
"Prototypes allow teams to explore solutions before committing to full development. They support value delivery by engaging users early to verify what is needed." (PMI Agile Practice Guide, Section 5.2 - Exploring and Confirming Requirements) Also:
"Engaging stakeholders in early solution validation through techniques such as wireframes or mockups reduces the risk of developing the wrong product." (PMI Agile Practice Guide, Section 3.4 - Delivering Value Frequently) Mike Griffiths reinforces this approach:
"Prototyping enhances discovery. It supports feedback loops that validate whether a feature adds value before it's built-especially useful when requirements are unclear." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 - Value-Driven Delivery) Why other options are less correct:
* A is a secondary benefit but not the primary goal of prototyping.
* B is speculative and does not reflect the sponsor's actual recommendation.
* D misrepresents the purpose of prototyping, which is for discovery, not accelerated deployment.