michaela-damm.jpg
blocshop
March 09, 2021
0 min read

Sprint Reviews and Sprint Retrospectives: What’s the difference?

Sprint Reviews and Sprint Retrospectives: What’s the difference?.png

When all the hard work of the current sprint is completed, it’s time to wrap up and prepare for the next one. Two processes that are beneficial to the team’s productivity and skill development are sprint reviews and sprint retrospectives. At first glance, these two official Scrum ceremonies look similar, but they're actually quite different.

What is a sprint review?

Sprint reviews take place after the sprint goal has been met, and before the next sprint planning session. The goal of each sprint is usually a functional increment, or deliverable. People who should attend these meetings are the stakeholders, Scrum Master and team, and the product owner. These meetings shouldn’t be any more than 4 hours, to keep them from being tedious. 2 to 3 hours should be enough to cover all the relevant topics.

Sprint Review Structure

  • Demonstration Stage

During this portion of the meeting, the developers or the product owner will present all the tasks the team completed during the sprint. Only increments that are ready to be released or implemented into the overall product are presented.

  • Stakeholders Discussion

The stakeholders, after seeing all the finished increments, are free to ask questions or provide feedback about the progress so far. During the discussion stage, there are three objectives to focus on.

  • Progress analysis - The Scrum team explains what exactly they did during the sprint, as well as any unfinished tasks. If applicable, they also explain the reasons for any unfinished work.

  • Market presentation - It’s the stakeholders’ turn to present now. The Scrum team explains the technical side of things, whereas the stakeholders explain the current market landscape and customer insights.

  • Motivation - This stage serves to motivate the Scrum team with positive facts and market projections so that they'll start the next sprint with enthusiasm!

  • Backlog Update

Once the stakeholders discussion is over, it’s time to update the backlog. This step is crucial because it provides structure and organization to the remaining increments that are to be completed. The product owner and Scrum Master add or remove user stories, and reprioritize the backlog items before choosing what the team will work on in the next sprint. The team uses different backlog prioritization techniques to achieve that. Read more on this process in the "Epic, Story, and Tasks in Agile" article.

What is a sprint retrospective?

As a part of the sprint cycle, sprint retrospective meeting also takes place between sprints, but it always comes after the sprint review. Those who should be at the meeting include the Scrum master, product owner, and the Scrum team. Thankfully, the retrospective meetings are shorter, usually lasting between 30 minutes and 3 hours. The purpose of a retrospective is quite different from a review. Rather than focusing on details of the project, this Scrum ceremony is to examine the team’s work styles and what areas they can improve in.

Sprint retrospective topics

There are three open-ended, existential questions that make up a sprint retrospective. Each team member must provide feedback for every question, if they can. This way, everyone has input and feels encouraged to share their thoughts. The questions are quite simple.

  • What went well?

  • What didn’t go so well?

  • What can we do to improve?

It’s easy to get answers to these questions and move on; the real challenge that many teams face is actually using the insights to make change. To make these meetings worthwhile, they must also make an action list. An action list is basically a list of the issues, and the things people can do to move towards solving them. Though this process is helpful for many, some choose to opt out entirely.

The problem with retrospectives

While retrospective meetings can be helpful to many teams, others choose to have them less often, or not at all. There are a few commonly reported reasons for this.

  • Tension or arguing - Sometimes people don’t respond to criticism well, or people fall into playing the blame game. Obviously, this is unpleasant for all parties, and could harm the team’s relationship rather than help it.

  • Takes too long - People may feel that having an hours long meeting takes too much time away from their other work.

  • Too repetitive, lacking ideas - The structure of the meeting might be tedious for some, who ran out of ideas on how to improve long ago.

  • Feeling unheard - If the team leaders or other members fail to use the ideas suggested in the last meeting, and nothing changes, people find that frustrating and demotivating.

To sum up, every team is different. The Scrum master knows their team best, and will make the best decision based on their needs.

Key Differences

As you can see, on the surface reviews and retrospectives sound similar, but they’re completely different. Here’s a summary of the biggest differences between the two.

  • Purpose

Perhaps the most crucial difference between these two Scrum ceremonies is their main objective. A sprint review is to share insights and progress about the project, whereas a retrospective probes the team itself and how they work.

  • Attendees

At a retrospective meeting, the Scrum team, Master, and product owner are present. In contrast, all those parties and the stakeholders, plus anyone else who may be needed, are present at a review session.

  • Length and frequency

The duration of sprint retrospectives depends largely on the team itself, and can last between 30 minutes and 3 hours, and some teams never have them. Reviews are usually between 2 and 4 hours, and should never be skipped.

  • End results

Just like the purpose of each ceremony is different, so too is the end result. The result of sprint review is more knowledge about the project and current market trends, a vision for the next sprint, and an organized backlog. The results of a retrospective should have an action list, and more insight into how team members work together and as individuals.

Blocshop provides custom-made software to businesses across the globe using certified Agile practitioners. If you or your company are interested in learning more about what Blocshop can do for you, have a look at our customer testimonials.


Learn more from our insights

roro665_data_transformation_from_one_format_to_another_with_g_91332f66-93b0-48d8-9d5e-a8609529cbb7_3.png
September 25, 2024

Generative AI-powered ETL: A Fresh Approach to Data Integration and Analytics

ETL meets generative AI. See how AI-powered ETL redefines data integration and brings more flexible data processing and analytics across industries.

roro665_uk_pensions_dashboard_reform_magazine_cover_collage_-_1888e056-80f6-4aac-958c-bf02b128a7d3_1.png
September 03, 2024

UK Pensions Dashboard Compliance: Deadlines, Transition Steps, and the Use of AI-driven Data Mapping

How AI-driven data mapping can support UK Pensions Dashboard compliance. Understand key deadlines and steps for efficient data conversion and transition to the UK Pensions Dashboard.

roro665_a_cover_image_depicting_data_conversions_and_compliance_c8ddf35a-cc0f-447a-abb7-0f4b1f14bb64 (1).png
August 23, 2024

Using AI for data conversion and compliance in the banking sector

Discover how AI transforms data conversion and compliance in the banking industry, optimizing processes while managing risks.

ai_applications_in_banking_and_banking_technology_blocshop.png
August 14, 2024

AI Applications in Banking: Real-World Examples

Explore how major banks are using AI to enhance customer service, detect fraud, and optimize operations, with insights into technical implementations.

20221116_153941.jpg
July 31, 2024

From Concept to MVP in Just 12 Weeks with Blocshop

Blocshop delivers your MVP in 12 weeks, solving real pain points with agile sprints, daily scrum meetings, and fortnightly reviews. Here's the process explained.

chatgpt4_ai_integration_blocshop-transformed.png
July 19, 2024

ChatGPT-4: An Overview, Capabilities, and Limitations

The technical aspects, usage scenarios, and limitations of ChatGPT-4, including a comparison with ChatGPT-4o.

roro665_depict_a_data_sample_thta_completely_changes_its_form_725a4f20-ea40-4dd1-a68d-5c4327c9bf24_1.png
June 20, 2024

Generative AI used for data conversions and reformatting

How to use generative AI for data conversion, addressing integrity, hallucinations, privacy, and compliance issues with effective validation and monitoring strategies.

DALL·E 2024-05-30 09.37.01 - An illustration suitable for an article about ISO 20022. The scene should feature a modern, sleek representation of the ISO 20022 logo in the center. .webp
May 28, 2024

ISO 20022 Explained: A Comprehensive Guide for Financial Institution Managers

What is ISO 20022? How does it affect companies and institutions in the fintech and banking industry and how to prepare for its adoption? All explained in this article.

DALL·E 2024-05-22 20.55.08 - A detailed and high-quality DSLR photo of a person using a laptop to shop online, showing personalized product recommendations on the screen. The back.webp
May 16, 2024

Key AI Trends in E-commerce and Overview of AI integrations for E-commerce Platforms in 2024

Transform your e-commerce platform with AI tools for personalization, analytics, chatbots, search, and fraud detection. Boost sales and improve customer experiences.

eIDAS mark.png
May 09, 2024

Digital Identity and Payment Services in the EU in 2024: Key Updates

eIDAS 2.0 and PSD3 are set to enhance how digital identities and payment services are managed across the European Union in 2024. Here’s an overview of how each framework contributes to the digital landscape of the EU, what to expect, and how to prepare.

eIDAS 2 in fintech and open banking EU market.png
May 06, 2024

What is eIDAS 2.0 and EU Digital Identity Wallet and how will it change the EU digital market

Learn how eIDAS 2.0 and the EU Digital Identity Wallet will transform digital transactions and identity management across the European Union.

best large language models for ERP systems.png
March 31, 2024

Language Models Best Suited for Integration into ERPs

Four prominent large language models stand out for their compatibility and effectiveness in ERP system processes and automation. See what they are.

PSD3 in open banking Blocshop.png
April 23, 2024

PSD2 vs. PSD3: The Evolution of Payment Services Regulation

What is PSD3 in open banking? See how PSD3 compares to PSD2 and what should banks and fintech businesses do to ensure regulatory compliance in the EU market.

roro665_hands_working_with_a_laptop_in_a_modern_office_there_is_20dca307-c993-4539-99d7-fd5ca264248c.png
April 14, 2024

Enhancing ERP Systems with AI Chatbots

Explore how AI chatbots can transform ERP systems, enhancing efficiency, decision-making, and user interaction.

eIDAS in fintech and open banking EU market.png
April 29, 2024

eIDAS: The regulation helping secure Europe's digital future

See how eIDAS enhances EU digital transactions with secure identity verification, supporting e-commerce and public services across Europe.

hybrid ERPs.png
March 21, 2024

Hybrid ERP: An Innovative Approach to Enterprise Resource Planning

Hybrid ERP is a blend of cloud and on-premise solutions. With expertise in both, Blocshop is uniquely positioned to help you with hybrid ERP development and implementation.

0-4 cover.png
October 03, 2023

IT Staffing: Individual Hiring vs. Specialized Developer Teams

Should you hire individual developers or go for a specialized, custom-built developer team?

chatgpt-35-limitations.jpg
July 17, 2023

ChatGPT-3.5: An Overview and Limitations

In this article, we'll take a closer look at the capabilities and limitations of ChatGPT-3.5, providing you with a comprehensive overview of what it can do and what its boundaries are. So, let's delve into the inner workings of this large language model.

gpt4 vs gpt3-5 and the key differnces.png
June 15, 2023

A Deep Dive into GPT-4 vs GPT-3.5 Differences and Ability to Revolutionize Software Development

There are key differences between ChatGPT-3.5 and ChatGPT-4 that software developers and companies procuring software solutions alike should be aware of. Let's see how these differences affect the output generated by these models on specific examples.

ai-development-cto-2023.jpg
May 09, 2023

AI-powered software development: What CTOs need to know in 2023

As technology continues to evolve at a rapid pace in 2023 and beyond, CTOs must stay ahead of the curve by utilizing predictive analytics, automated testing processes, and deployment solutions.