We have gone through three Scrum events so far - Dart , Sprint Planning , and Daily Scrum . These three events cover the execution part of Dart. Merely how do we end the Sprint? How do we demonstrate (and at times take sign-off) the piece of work washed during the Dart? The answer to all these is the Dart Review Event .

In this tutorial, we volition go through the below topics.

  • What is the Sprint Review?
    • Who participates in Sprint Review?
    • How to conduct a Dart Review?

What is the Sprint Review?

The sprint review is a Scrum Event that takes place at the end of the Sprint to inspect the increment and adapt the product backlog .

Sprint Review

The Sprint review allows all the stakeholders to audit and conform to what's already built. It provides a transparent view of the current state of the product, and gives a platform to ask questions, give suggestions, and have discussions on how to move frontward based on the current situation.

Like every other scrum event, the Dart review is also a time-boxed consequence . The elapsing is a maximum of 1 hour for every week of Sprint elapsing. So for a Sprint that is 2 weeks elapsing, the Sprint review meeting should be a maximum of ii hours.

As a general exercise, the Dart review finishes on the concluding day of Sprint. It'southward important to note that the sprint review is not a " Demo ". While the squad showcases what they take washed, the purpose is to collaborate as a group, take feedback, and determine on how to move forward.

Who participates in Sprint review?

Equally the purpose of the sprint review is to take feedback from the stakeholders, all the people who have a stake in the sprint deliverable must attend the review meeting.

Scrum Team

Scrum Team ( Scrum Master , Scrum Development Team , and Production Possessor ) must nourish the sprint review. They collectively need to collaborate with other stakeholders, and answer any questions and have feedback and adjacent steps.

Internal Stakeholders

These are people within the organization that have a stake in sprint deliverable. These could be plan managers, other scrum masters, marketing, sales, IT Support, Business development teams, etc.

External Stakeholders

Though it's not very mutual, the Product possessor may invite people exterior the arrangement for a dart review. Due east.grand., the team is enhancing a website where agents tin book tickets for their clients. In such a case, the squad can invite some agents and then that they can accept a first-paw wait at the product, and they can provide feedback much early in the life bicycle.

How to Conduct a Sprint review?

Sprint Review

Sprint review has a larger audience, so it's vital that the coming together is planned well and executed well. Nosotros will have a wait at the planning activities that need to happen before the review meeting. We volition also look at the best practices and steps that need to finish during the meeting (execution)

Preparation Activities

These are the activities that need to terminate before the sprint review meetings. Information technology includes figuring out whom to invite, sending out the invites, confirming that all work is washed, and planning for a sit-in.

1. Place the Attendees

The kickoff step in grooming is to place who all needs to attend the dart review. We know that the Scrum team is mandatory to participate in, but it's important to invite all the stakeholders. Unremarkably, based on the broader goals that the team is trying to achieve, at that place volition already be a ready of stakeholders that will join every meeting. East.g., if the team is building an application that will collect user feedback for a production across all channels (FB, Twitter, emails, etc.), then the marketing team is a key stakeholder. They should be nowadays in all the sprint review meetings. All the same, some sprint reviews need a specific set of stakeholders based on what we achieved during that Dart. East.1000., if the squad has delivered capturing feedback via the emails that the IT back up squad gets, then merely for that sprint review, the IT back up team becomes a stakeholder.

In Summary, it'due south essential to identify all the stakeholders that demand to nourish the sprint review. It helps in early feedback, and also helps in easy credence and usage of the deliverable.

2. Sending out the invite

Nosotros have already identified the stakeholders, so we now need to send out the invites. The sprint review carries out on the last day of Sprint. Usually, the sprint duration is consistent (say two weeks), so the invite should be sent as a recurring invite every two weeks. It's also important to keep timing the same (say 4-5 pm of final day) and transport it for weeks in accelerate. While this seems similar a straightforward activity, information technology must be sent in advance and at the same time. It helps all stakeholders plan, and in that location will not be a request to re-schedule.

3. Are we done with all the work?

It's vital to ostend if all the piece of work is completed (especially what was supposed to achieve last day) and update the Jira lath (or any other software). Information technology will help in presenting all the stakeholders with an accurate picture of what completes. Y'all don't desire to land in a situation where yous say that it's finished but not reflecting on board.

If at that place is whatever work pending, that we should marking so that we tin give a transparent view to all stakeholders that this work will sideslip to the next Dart.

It's the responsibility of the development squad to demonstrate ownership of the " Done " increment.

4. Ready for Demonstration

It'due south essential to nowadays the dart review as I team. What this means is a articulate programme and gild in which the team will present. Usually, the Production Owner starts by talking about the goals of the Dart and what functionality is delivered. The Scrum Primary tin can testify fire-down charts and the velocity of the team. After which the development squad volition showcase their work. It'southward e'er good to make up one's mind before-hand the club in which its presentation will happen and if we need to prep annihilation (E.thousand., setup whatever specific information, etc.).

It'southward too encouraged that most (if not all) team members go to nowadays what they have achieved during the Dart. It is not a good practise that one-2 team members present the team's work.

Execution of the Dart Review

Now we are done with all preparation activities. It'southward time to execute the sprint review meeting. There are best practices that need to follow to conduct review meetings effectively.

1. Summarize the work washed in Sprint

The Sprint review starts with the Product Owner presenting the sprint goal set for this Dart. PO also presents the backlog items that associate with this dart goal. The product owner explains what Product Backlog items have their status as " Washed " and " Not Washed ". This information gives a good view to all stakeholders of the accomplishment in this Sprint against sprint goals defined.

ii. Demonstrate the Work

The development squad will demonstrate the work whose status is " Done ". They also talk about the challenges they faced and how they resolved them. The evolution squad will answer any questions that the stakeholders may have on whatever of these work items.

At this betoken, it'south essential that the discussions remain focused on the work at hand and not deviate from anything not relevant. Scrum Primary needs to pitch in to park whatever such discussions and remind the squad that information technology's a time-boxed meeting and demonstration of all the work that needs to complete.

3. Discuss and Adjust

The dart review is an opportunity for a shared understanding between all the stakeholders - The people who create information technology (Scrum Squad) and the people who benefit from it (End Users, Customers, and other stakeholders).

The product owner discusses the product backlog as per its electric current status. PO also presents the target dates and crude milestones on what will come upwardly in subsequent sprints. The entire group deliberates on what to do no side by side. The basis of this discussion is what work needs to cease (including any spillovers from the current Sprint). Equally a group, the team discusses the priority items that we should take in the adjacent Sprint. The stakeholders (like the Marketing team) could provide valuable insights into how the potential use of the product might accept changed based on market place conditions, and in that context, what makes the nigh sense to selection upward side by side.

  • The product owner will take this feedback and accommodate the product backlog and prioritization appropriately.
  • The Scrum Master tin also talk near the squad'south velocity and how the team is improving every Sprint, which also feeds into how much work can terminate in subsequent sprints.
  • The sprint review meeting ends with a shared understanding between all stakeholders about the accomplishment of work then far, how much work is pending, and how the prioritization of work happens for upcoming sprints.

Common Questions on Sprint Review

Now that nosotros have got a good understanding of the Sprint review result let's discuss some of the common questions and doubts that people have on Dart review.

What happens if the Product Owner is not available during Sprint Review should we re-schedule to another day?

Ideally, the Product possessor should always be present in the Sprint Review, but in that location can exist instances where the PO cannot attend due to holiday or other reasons. In such circumstances, it's essential that the team nevertheless goes ahead with the review.

Recall - the Sprint review is not just virtually the Scrum team, it's as well most all the stakeholders who are going to attend, so it's essential to keep the discipline and honor the fourth dimension that everyone has committed.

The Scrum Master tin can have the lead to present the goals and calls out what to accomplish and what piece of work is remaining. The team can accept annotation of feedback that stakeholders may accept on prioritization, and pass information technology on to the Product owner.

What happens if no meaning work accomplished during the Dart - Should we cancel the Dart review?

Although not common, the possibility is that the squad couldn't complete the work, and there is not much to testify to the stakeholders. As such, it's common to think that the sprint review should get canceled, as non to waste the time of stakeholders.

However, it'southward important to note that demonstrating work is just ane attribute of dart review. Collaborating with a grouping on what to do adjacent is another crucial attribute.

So in such a case, the squad should still go alee with the Sprint review. Talk over why the work couldn't complete. The squad too needs to call out how they will incorporate the learning so they tin can do better next time. As a group, the team and stakeholders tin deliberate on the prioritization of remaining work (including current spillovers). The Scrum Master can talk about velocity , to run into if the work can however complete in the remaining sprints. Additionally, SM will check if in that location is a need for course correction (E.yard., de-prioritizing some work, or adding additional team members, etc.).