Several new stakeholders are concerned about being asked to review a product demo before it is complete. How should the agile coach explain to the stakeholders the value of working this way?

The primary value of a product demonstration (Sprint Review) before the product is "complete" is to create a fast feedback loop. It allows stakeholders to see a tangible, working increment of the product and provide input. This immediate feedback is crucial for validating or correcting the team's assumptions about the requirements and the solution. This process of inspection and adaptation ensures that the product being built aligns with stakeholder needs and delivers the expected value, allowing for course correction in subsequent sprints.

A. The goal is to increase direct stakeholder involvement and feedback, not to suggest they can be represented by a proxy.
B. The demo focuses on the product increment and its value ("what" was built), not on the team's estimation accuracy or understanding of effort.
D. While the long-term goal is a worthwhile return on investment, a single demo is a tactical meeting to inspect the increment and adapt the plan.

1. Project Management Institute. (2017). Agile Practice Guide. Section 5.2.7, Demonstration/Review, p. 60. "The purpose of the demonstration is to get feedback from the product owner and other stakeholders on the increment... This feedback is then incorporated into the product backlog for consideration in a future iteration."

2. Rus, I., & Lindvall, M. (2002). Knowledge management in software engineering. IEEE Software, 19(3), 26-38. https://doi.org/10.1109/MS.2002.1003450. This paper discusses how agile practices facilitate knowledge sharing and learning, with reviews and demos being key mechanisms for validating knowledge and assumptions between developers and customers.