What is one important aspect of the Sprint Review?

The importance of discussing what did not get done during the Sprint at the Sprint Review lies in the transparency and adaptive nature of the Scrum framework. This aspect allows the team to openly communicate the challenges they faced, identify obstacles, and gather feedback from stakeholders on the incomplete items.

By addressing the unfinished work, the Scrum Team can foster a collaborative environment where insights and suggestions can be gathered. This discussion helps the team and stakeholders align expectations and understand the context behind any incomplete items, which can lead to valuable learning and continuous improvement in subsequent Sprints.

Sharing what was not achieved also opens the door for stakeholders to contribute their thoughts, which can inform future planning and potentially adjust priorities or strategies. This aspect emphasizes the essence of an iterative process, promoting a mindset of learning and adaptation rather than solely focusing on finished work.