The Sprint Review is an informal meeting where the team demonstrates the product and determines what is ready and what is not, in other words it is a meeting to demonstrate and determine the usability of a software.
Agile software developmentIt has been an efficient way to develop digital products in recent years and it is a mandatory pillar of your digital transformation for your company to become a great digital product company. ThatADAPT® methodologyis a unique digital product development framework to ensure the success of leaders in the digital age.
Society has changed and leaders need support in the way they lead and shape their digital product organizationsADAPT® methodologywas created, but now let's dive into the sprint review meeting.
AGILE DEPLOYMENT GUIDE
Do you want to build an agile, flexible and fast company, but don't know where to start? The Agile Implementation Guide was created on the basis of several years of agile implementations in Europe!
DOWNLOAD THE GUIDE
The sprint review meeting takes place after the completion of the sprint. It is planned to check the increment and adjust the product backlog if necessary. When the Sprint Review Meeting takes place, the Scrum Team and stakeholders review what was done during the Sprint.
The review is for information sharing, not a status meeting. This is done solely to receive feedback and ensure collaboration.
during onehustle, a regular sprint review meeting is scheduled to demonstrate and determine the usability of the product. Teams are expected to deliver shippable product during each increment or sprint.
To ensure success, a sprint review meeting is held at the end of each sprint. During the review, the Scrum Team shows the stakeholders what they have accomplished by demonstrating the redesigned features.
Sprint review meetings are intentionally informal. Programs such as PowerPoint are prohibited and a maximum preparation time of 2 hours is set. These meetings are not, and should not be viewed as, a major distraction or distraction for the team. Instead, they should be a natural transition and the result of the sprint session.
Typically theScrum-Master, members of the management team, the product owner, customers, developers of other projects, and the scrum team attend the sprint review meeting.
At the sprint planning meeting, a goal is set for the software. Achieving this Sprint Goal is very important. To ensure this, the delivered project is evaluated during the sprint review and compared to the goal. Each product backlog is also included in the review to ensure the goal has been met.
Accelerator for digital leadership
Do you want to start a digital products business but don't know where to start? Our Digital Leadership Accelerator shows you how! Become a recognized digital leader in your industry by leading your digital products business!
In a sprint review meeting, the Scrum Team and stakeholders discuss the work done during the sprint. After evaluating the work done along with the changes made to theproduct backlog, the group is working on what steps should be taken next to optimize the value of the software. These meetings are always intentionally informal to keep the group focused and encourage feedback and collaboration.
For month-long sprints, review meetings should last a maximum of four hours; so-called time-limited sessions. When the sprint sessions are shorter, the review meetings are also shorter.
ThatScrum-Masteris responsible for scheduling the meeting and informing all participants of the purpose of the review. ThatScrum-MasterThey are also responsible for keeping the meeting on schedule.
The sprint review meeting should include:
- Presence and participation of the Scrum Team, the Product Owner and the invited key stakeholders.
- Thatproduct ownermust report the items in the Product Backlog; which backlog items have been completed and which have not.
- Thatdevelopment teamdiscuss what went well and what problems arose. They should also tell the group what they did to solve the problems.
- The development team demonstrates their completed work and answers questions about their increment.
- The Product Owner leads the discussion of the Product Backlog in its current state. They set projected completion dates based on the progress of the sprint session.
- To make a valuable contributionSprintplanung,The whole group determines the next steps during the Sprint Review meeting.
- This is a time to review possible changes in the market, the valuation of the project, and the areas considered most valuable. The next steps should also be outlined.
- Review the timeline, budget, potential capabilities, and market to determine the next expected product release.
At the end of the sprint review meeting, product backlog reviews should be conducted to further define potential backlog items for the next sprint session. The Product Backlog can be fully customized to introduce new opportunities.
Focus on the end user
Businesses may be reluctant to engage end-users for a number of reasons: some fear expanding reach, others believe they shouldn't ask end-users to engage, while others don't know who their end-user is. End users are an important part of the session. Never find an excuse not to include them!
Involve the product owner
Too often many companies organize their Sprint Reviews as a team presentation for the Product Owner to evaluate or judge their work. This format is complete nonsense! Sprint Reviews are not inquisitions or courts of law, but rather informal gatherings to collect customer feedback.
Rather than presenting their data to a judge-like product owner, teams should work with the product owner to review each full story.
At the beginning of the Sprint Review, the Product Owner should be the first to greet everyone and give an overview of the project. The owner can then discuss the sprint goals: what has been achieved and what has not been achieved.
It's also a good time to talk about product quality, software release, and product exhaustion. The owner can point out what reviewers should look out for and tell the team how to provide feedback.
After they finish their introductory explanations, the Product Owner can turn the meeting over to the Scrum Team to demonstrate the functional capabilities of the software.
Understand group dynamics
group dynamicsThey are transformed significantly when the focus of the meeting changes from a single Product Owner to a collaborative group that includes the Scrum Team, stakeholders, and end users.
When the product owner becomes part of the release team, the previous roles change. Here's a look at how each group is affected.
The role of the product owner changes to that of the actual owner of the product. As a key member of the team, the owner takes more responsibility for the product. You are responsible for decision making and presenting the results to end users and prospects. He stands up and introduces the product increment and gives an insight into the status of the project.
By changing the role, the owner understands that they become more disciplined in maintaining product design, eliminating burnout, and setting a quality level for work.
Another notable by-product of this change is that deviations are immediately visible. When owner-perceived revisions to end-user requirements do not match actual requirements, this becomes immediately apparent.
The Scrum Team has a greater sense of pride and accomplishment and is better positioned to demonstrate their work to the group. They are given end-user time and, at best, meet end-users face-to-face.
Knowing the end user is the best way to develop quality software that provides the greatest benefit to the end user. By learning to accept feedback in every sprint session, the team gains more appreciation for the product owners and customers.
The team will also feel less judged or qualified by the product owner. You will leave the meeting more energetic and motivated for the next sprint.
WEBINAR FROM PROJECT TO PRODUCT
Learn the critical strategy for building the most successful digital product companies. A must-attend webinar for any executive serious about building a digital products business.
REGISTER FOR THE WEBINAR
Company executives / prospects
When leaders and stakeholders are part of the review meeting, they can see the teamwork while engaging in a real review of the work done and actions taken. In addition, end users can personally inform executives/stakeholders about their needs.
Above all, they learn to behave appropriately. The dynamics of these meetings differ significantly when customers are part of the session.
When end users are present, executives and stakeholders spend less time arguing and criticizing each other. Instead, everyone shows their best behavior and ensures that the review is more motivated and productive.
Without a doubt, end users are the stars of review meetings because they spend valuable face-to-face time with software developers. You spend so much time with the development group that end users feel a sense of ownership.
Because they put so much time and dedication into developing the project, the users become the biggest supporters of the company. This knowledge gained is valuable in reducing the flood of support calls that are common after a release.
ThatScrum-Masterfacilitates the Sprint Review Meeting. This person creates an environment among all members so that great achievements and goal achievement can arise. For this to happen, theScrum-MasterYou need to make sure the right people are present at the meeting. He/she must also ensure that the right space and materials are available.
Other little things like ordering food and drinks are also the responsibility of theScrum-Master. While this may seem like little to some, food is the fuel teams need to keep their hard work going during meetings. Personally, I had a lot of great conversations with the teams over lunch.
One thing to note, this is not the caseScrum-Master's show - you're not the star. ThatScrum-MasterHe is there to support the team. They also welcome end users and make sure they're onboard, have a chance to be heard, and be behind the scenes.
To master the art of feedback, you must first create an environment that allows open feedback. Involving end users in sprint review meetings can be daunting, but remember: Hearing feedback early gives you time to make necessary adjustments.
Waiting until the end to find out you went the wrong way is a waste of precious time and resources. So if you're still worried about the scope drifting, don't be. During the review, the product owner first decides what rewards will be given after each Sprint Review.
You can take this opportunity to learn more about what end users need and don't need; This helps reduce and eliminate the overproduction of some features that are never used.
By focusing on the end user and building energy and enthusiasm, create a sprint review meeting that customers want to attend. It's easy to do; Just set up a patch that provides direct value to the end user. Once that's done, just sit back and listen. You'll be surprised at what you learn.
Did you like this article?
We enable leaders to be valued and recognized to make a difference in the world by helping them ffrom project-oriented to product-oriented organizations, we do this by applying our ownADAPT® methodology.
If you want to know how we can help you, visit the page:work with us.
Will you succeed or fail as a design leader for your digital product company?
If you would like to find out more about the maturity level of your company's digital product development, simply access this scorecard. It will help you identify all the different areas that you can improve and build a real digital products company.
What is a sprint review meeting? ›
The sprint review is an informal meeting where the team gives a demo of the product and will determine what is finished and what isn't, in other words, is a meeting to demonstrate and determine the usability of a piece of software.What questions to answer in sprint review? ›
- What questions do you have?
- How would you use this product?
- What excites you about the product increment we reviewed? ...
- How do you feel about the product increment we reviewed? ...
- If you could change one thing about the product we've built, what would you change?
Here are items that you would typically see on a sprint review agenda: Welcome and housekeeping. Sprint status. Review of top requirements and key.What is sprint review in simple words? ›
A sprint review is an informal meeting held at the end of a sprint, during which the team shows what was accomplished, while the stakeholders provide feedback. It's a collaborative working session rather than a one-sided presentation.What is the main purpose of a sprint review? ›
The sprint review's purpose is to inspect the increment that was developed in that sprint and collect feedback from key stakeholders. The sprint retrospective is to inspect and improve the agile practices that were followed during the sprint. Both are distinct and essential for a Scrum team to function well.How can I make sprint reviews more fun? ›
- Talk in the user language: The end-users –both the PO and the stakeholders– are a vital part of this meeting. ...
- Team members should present their own User Stories: This is my special signature and is something that is not often done that adds a lot of value to the team.
The product owner begins the meeting by sharing the product goal and explaining what the scrum team aimed to accomplish during the sprint. This part also covers a review of the original sprint goal and which product backlog items were part of the sprint.What happens during a sprint review *? ›
Sprint review is an informal meeting held at the end of the Sprint where the increment is presented to promote the collaboration and obtain the customer's feedback on the developed product. It is mainly conducted to 'Inspect' the Increment and 'Adapt' the Product Backlog if required.What is the primary focus during the sprint review choose the best answer? ›
The primary objective of the Sprint Review is to demo the Sprint work and to receive feedback from the Product Owner(s) on the work completed in the Sprint.What are the 4 steps within a sprint? ›
That's why you need a repetitive process that you can follow each time you have to take on a new sprint. Technically, every sprint is made of four steps: planning, execution, review, and retrospective. This is what makes up the sprint cycle.
What is the most important part of a sprint review? ›
Giving a demo of the product
This is widely considered as the main purpose of a sprint review. Developers have the opportunity to show product owners and stakeholders the changes they have implemented.
An effective Sprint review meeting agenda should cover new features, sprint impediments, and an assessment of whether the sprint goal was achieved. Sprint reviews typically last two to four hours and feature a product demonstration where a working version of the latest increment is presented and inspected.What makes a story ready for sprint review? ›
Definition of Ready for a sprint:
Prioritized sprint backlog. Defects, user stories and other work the team has committed to are contained in the sprint backlog. No hidden work. All team members have calculated their individual capacity for the sprint.
Sprint Review focuses on the product, while Sprint Retrospective focuses on the process. Sprint Review is concerned primarily with optimizing and maximizing product value, whereas Sprint Retrospective is involved with people, processes, and tools.What should we not do during sprint review? ›
Hold meeting without Product Owner – Because many teams do not understand the goal of the Sprint Review, the Product Owner may often be considered an optional attendee. This is a big mistake that should be corrected immediately since the Product Owner is a key person that the team relies on for feedback and direction.How do you make a meeting review interesting? ›
- 1 Ice breakers. ...
- 2 Show-and-tell. ...
- 3 Let people take ownership. ...
- 4 Celebrate team wins. ...
- 5 Encourage shoutouts. ...
- 6 Play an online game.
- Prepare ahead of time.
- Look to the future.
- Ask the right performance review questions.
- Be intentional with what you say.
- Practice active listening.
- Discuss next steps.
Participants in the sprint review typically include the product owner, the Scrum team, the ScrumMaster, management, customers and developers from other projects. During the sprint review, the project is assessed against the sprint goal determined during the sprint planning meeting.How many hours is sprint review? ›
Sprint reviews are limited to a maximum of four hours. The general rule of thumb is to allow one hour for sprint review every one week of sprint length. That means teams should timebox sprint review to two hours for a two-week sprint and four hours for a one-month sprint.What is the first thing done in a sprint? ›
The first thing the team must do is therefore to plan which items from the Product Backlog should be worked on in this Sprint, so that the best value can be delivered by the end of it.
What is sprint planning checklist? ›
The Sprint Review Checklist:
Clean up the board, engage the whole team. 2. Create a subsequent Sprint Backlog in the project management tool. 3. Check the statuses of each ticket, move tickets if necessary (focus on moving tickets to be done, and to next Sprint Backlog or to Product Backlog).
The first sprint activity is sprint planning. In the sprint planning meeting, the development team plans and agrees on the product backlog items they are confident they can complete during the sprint, and identifies the detailed tasks for delivery, according to the team's definition of done.What are the 3 types of sprint? ›
In a track and field competition there are generally three different sprint distances: 100m, 200m, and 400m. The original Olympic event, the stadion race, was a sprint of around 180m. A sprint race starts out with the runners in starting blocks in their lane. The official will say "on your marks".What is the most important element in sprint events? ›
Perfecting your sprint starts (especially when using blocks) is arguably the most important aspect of the acceleration phase as it will affect your overall efficiency throughout the race.How do you present sprint goals? ›
The Product Owner should share the draft Sprint Goal during the first part of Sprint Planning, or even asynchronously in advance. It is up to the Product Owner to explain why this objective will create customer value and to clarify how the goal serves the long-term vision and roadmap.What is the main agenda for the sprint planning meeting? ›
Every sprint planning meeting agenda should include discussions about the ultimate objective of the sprint and the team's capacity, followed by a granular look at the sprint backlog, before you start slotting tasks into the sprint.Who facilitates sprint planning? ›
A scrum master or coach typically facilitates sprint planning in order to ensure that the discussion is effective and that there is agreement to the sprint goal and that the appropriate product backlog items are included in the sprint backlog.What is the purpose of a sprint meeting? ›
A sprint planning meeting is a working session for scrum teams to align on what will be accomplished during the next sprint and how the work will be completed. The development team and product owner collaborate to prioritize work and regroup around sprint goals.What is the difference between sprint review meeting and retrospective meeting? ›
Sprint Review focuses on the product, while Sprint Retrospective focuses on the process. Sprint Review is concerned primarily with optimizing and maximizing product value, whereas Sprint Retrospective is involved with people, processes, and tools.How do you facilitate a sprint meeting? ›
- Start with the big picture. ...
- Present new updates, feedback, and issue. ...
- Confirm team velocity and capacity. ...
- Go over backlog items. ...
- Determine task ownership. ...
- Confirm new issues, impacts, and dependencies. ...
- Reach a group consensus. ...
- Officially begin your sprint.
What two main topics does the sprint planning meeting cover? ›
- The What – The product owner describes the objective(or goal) of the sprint and what backlog items contribute to that goal. ...
- The How – The development team plans the work necessary to deliver the sprint goal.
- What helps you to be successful as a team?
- How did you do this sprint?
- Where and when did it go wrong in this sprint?
- What do you expect, from who?
- Which tools or techniques proved to be useful? ...
- What is your biggest impediment?
- If you could change 1 thing, what would it be?
A sprint review is a formal meeting between the Scrum team and stakeholders to discuss work completed and to address any concerns. A sprint retrospective focuses more on improving the sprint process as a whole.