The Scrum Team is feedback oriented

In the Sprint Review, the Scrum Team members interact with the customers and other relevant people about the results of the work done during the Sprint. The main goal of the meeting is to get feedback from these people on the Increment or Increments that were implemented. The Developers and Product Owner present and demonstrate what is done, according to the Definition of Done, and encourage the others present to try the new features, ask, and receive questions, offer answers, and take notes.

The external people present at the meeting are preferably best suited to provide feedback on what has been produced in the Sprint, such as the customers or direct users of the items that have been implemented. In this way the feedback obtained at the meeting becomes valuable, serving as raw material to update the Product Backlog for subsequent Sprints and allowing the product to be adapted in order to generate the next greatest value.

During a Sprint, the Developers can also seek early feedback from the Product Owner, customers, and others on what is already done.

The most powerful feedback, however, comes from the product usage metrics that are collected by the Developers and defined in collaboration with the Product Owner. By allowing the product to reach users frequently, we make it possible to measure how these users are utilizing the parts of the product that are already in their hands. In this way, the Developers and Product Owner can understand how to modify and evolve the product to better meet the users’ needs and to also understand what would or would not be worth building next, which is then fed into the Product Backlog. As I stated earlier, use defines the product.