One of the pivotal events within the Scrum framework is the Sprint Review. This blog post will delve into the Sprint Review event and shed light on two key considerations: the importance of creating valuable increments through vertical slicing and the significance of showcasing "done" work while discussing the direction of features.

Creating Vertical Slices for Valuable Increments In Scrum, the primary objective is to deliver a valuable product increment at the end of each sprint. The way user stories are written and sliced greatly influences the ability to create such an increment. Traditional approaches to software development often result in horizontal slicing, where each layer or component of functionality is built separately. However, in Scrum, the focus is on vertical slicing. Vertical slicing involves breaking down user stories into smaller, manageable units of functionality that provide end-to-end value. By prioritizing vertical slices, teams can ensure that each increment is potentially releasable and can add value to the customers. Instead of completing one layer at a time, Scrum teams work across the entire stack, incrementally building and refining the product with each sprint. This approach allows for earlier feedback and validation from stakeholders, reducing the risk of developing irrelevant features.

Sprint Review: Showcasing "Done" Work and Aligning Direction

The Sprint Review is a crucial ceremony in Scrum that provides an opportunity for the Scrum Team, stakeholders, and customers to inspect the work accomplished during the sprint. It serves as a platform for demonstrating the "done" work and engaging in meaningful discussions about the direction of the product increment. The term "done" can vary across different organizations. Some companies may define "done" as having the product available to the customer, while others may consider it as completing unit testing. Ideally, the closer the definition of "done" is to the customer, the better. This is because it requires fewer steps after the Sprint to reach the value state by making it to the rest of the customers. To put it another way, the shorter your DoD, the less Agile the team.

Regular Stakeholder Alignment

To ensure clarity and alignment, it is essential to have a well-defined "definition of done" at both the team level and the Scrum of Scrums (SoS) level. The team's definition of done establishes the criteria that each user story must meet before it is considered complete. The SoS-level definition of done outlines the criteria for integrating and validating the work of multiple teams. By aligning these definitions, and ideally making the team Scrum of Scrums’ definition of done as short as possible, the Sprint Review can accurately reflect the progress made toward the overarching project goals.

In addition to showcasing completed work, the Sprint Review event provides an opportunity for stakeholders to provide feedback and steer the project's direction. However, it's important to note that regular consultation with stakeholders should occur outside of the Sprint Review as well. Throughout the sprint, one-on-one meetings between the Product Owner and stakeholders can be conducted to gather quick feedback, refine requirements, and ensure the project remains on track. By involving stakeholders in these ongoing discussions, the Scrum Team can adapt and iterate effectively, ensuring that the product meets the evolving needs of the customers.

The Sprint Review event in Scrum serves as a crucial milestone for demonstrating completed work and engaging stakeholders in discussions about the product's direction. By prioritizing vertical slicing and creating valuable increments, Scrum teams can ensure that each sprint yields tangible outcomes that can potentially be released to customers. Furthermore, establishing a clear "definition of done" at both the team and SoS levels enables effective collaboration and alignment. Regular consultation with stakeholders throughout the sprint, outside of the formal Sprint Review, ensures that quick feedback can be addressed promptly, refining the product and delivering greater customer value. The Sprint Review event in Scrum is not just a ceremony to showcase completed work but also a forum for collaboration, feedback, and continuous improvement. It provides an opportunity for the Scrum Team to engage with stakeholders, gather insights, and make informed decisions about the project's direction.

By adopting the practice of vertical slicing, teams can ensure that each increment represents a valuable piece of functionality that adds value to the end users. This approach allows for early validation and feedback, enabling the team to course-correct and adjust as necessary. Vertical slicing also facilitates faster delivery of tangible features, giving the team a competitive edge by releasing valuable increments more frequently. During the Sprint Review, the Scrum Team demonstrates the work that has been completed and gathers feedback from stakeholders. The emphasis is not only on showcasing what has been accomplished but also on discussing the direction of features. This discussion ensures that the team and stakeholders are aligned on the priorities, vision, and goals of the project.

The concept of "done" is a critical aspect of the Sprint Review. It represents the level of completeness and quality that the team has achieved for each user story. However, the definition of "done" can vary across organizations and projects. Some companies consider a user story "done" when it meets the expectations of the end customer, while others consider it "done" when it passes all required tests and meets the team's definition of completeness.

To address this variation, it is essential to have a clear and agreed-upon definition of "done" at both the team level and the SoS level. The team's definition of done outlines the specific criteria that need to be met before a user story is considered complete, ensuring a shared understanding within the team. The SoS-level definition of done takes into account the integration and coordination of work across multiple teams. This alignment ensures that the work showcased during the Sprint Review aligns with the overall project objectives and satisfies the customers' needs.

While the Sprint Review is an important event, it should not be the only opportunity for stakeholder engagement and feedback. Regular consultation with stakeholders throughout the sprint helps in refining requirements, addressing concerns, and incorporating valuable input. One-on-one meetings between the Product Owner and stakeholders outside the formal Sprint Review provide a dedicated space for quick feedback and refinement.

In conclusion, the Sprint Review event in Scrum serves as a pivotal moment for the Scrum Team to showcase completed work, gather feedback, and align the direction of features. By focusing on vertical slicing and creating valuable increments, teams ensure the delivery of tangible functionality that adds value to the end users. Establishing a clear definition of "done" at both the team and SoS levels facilitates collaboration and alignment. Regular consultation with stakeholders throughout the sprint enhances communication and ensures that the product remains responsive to evolving customer needs. The Sprint Review event, combined with ongoing stakeholder engagement, drives continuous improvement and contributes to the overall success of the project in the Scrum framework.