Getting feedback
Agile projects are run with continual feedback built in. At the end of each period of work, known as a sprint, the customer is given a chance to see what has been built and feed back on what works and what doesn't. The project team also has an opportunity to receive feedback as part of a lesson-learned activity, whereby all the people working on the project can discuss what worked and what didn't and adjust accordingly for the next sprint.
Feedback is incredibly important to the success of a solution as the end goal is to create a solution that addresses the original business need and is usable. History is full of projects that failed simply because the resultant system was too difficult to use.
It can be challenging to accept feedback, but our role as architects is to help steer the business, and this is a two-way process of listening and adjusting.
For longer-running projects, business needs can change through the project. This is an inevitable consequence...