When the customer suggests changes during a demo that deviates from the agreed roadmap, how should the team respond?

The appropriate response in this scenario is to seek to accommodate the changes for customer satisfaction. This aligns with the core principles of Agile methodology, which emphasizes flexibility and responsiveness to customer feedback. Agile frameworks, such as Scrum, value customer collaboration over strict adherence to pre-defined plans. When a customer provides feedback or suggestions during a demo, it’s an opportunity to enhance the product based on real-time insights into their needs and expectations.

Accommodating the changes demonstrates a commitment to fulfilling customer requirements and enhancing their experience with the product. It fosters a collaborative atmosphere where the customer feels heard and valued, which can lead to stronger relationships and better outcomes in future iterations. The goal of Agile is not merely to deliver according to a set plan but to adapt and improve continuously based on stakeholder feedback.

In contrast, the other options do not prioritize collaboration or customer satisfaction. Ignoring the feedback disregards the customer's insights, which may lead to dissatisfaction or a product that doesn't meet their needs. Documenting the changes for later implementation might delay valuable adjustments that could be made sooner, thereby missing an opportunity for immediate improvement. Refusing any changes after the initial roadmap is established creates rigidity in a process that should be inherently flexible, risking misalignment with the customer’s evolving needs and priorities