17 retrospective sprint examples for exciting final sprints (2023)

Keeping your agile team engaged is critical, so testing a different one using different end-of-sprint retrospective examples can fix things. You want it to be as fun as possible. We spend a lot of time being serious at work.

Regardless of whether it is XP, Scrum(examples for scrum masters)Hindsight, Kanban, is one of the most important events for the success of a team.

The idea behindRetrospection is about finding out what went well, what could be improved, and what could have been done better.to help facilitate continuous improvement. The team will provide feedback on the progress of a project. It should be an open discussion where everyone gives their honest feedback.

There are several ways to run an agile retrospective event. The easiest way is to have all team members enter their feedback into a spreadsheet and then action is taken if the feedback calls for it. However, this method gets boring and that's why agile retrospective models come in.

The best retrospectives I've been to were the less serious, laid-back meetings. The team was comfortable with each other and didn't care what they said. As an Agile Coach, it is your responsibility to calm down the team.

Retrospectives bring a team together, providing an opportunity to celebrate what went well, but also to reflect on what could have been better and how to improve.

17 retrospective sprint examples for exciting final sprints (1)

Facilitate a Sprint Retrospective

The retrospective technique is short meetings that are held at the end of each team sprint. These meetings are great for building teams and also finding gaps in the development process. During the meeting, the teams should come together and share ideas.

The format should be as simple as possible:

  1. Start with icebreakerwhere they play simple games to bring members together and set the atmosphere for members to feel comfortable giving honest feedback
  2. setting the stagefeaturing retrospective themes and templates so members can be ready with their feedback
  3. combining ideasof different people on the team, giving each individual the opportunity to provide their contributions
  4. priority votewhere members see what matters most and what to expect
  5. stock tracking, how to solve the problems that arose in the process of project execution

After each release/iteration, the Scrum Master/Team Leader must perform a retrospective which can also be called an intraspective. The purpose of the retrospective is to improve methods and teamwork by reviewing the previous iteration/release. There are 3 core questions that need to be answered in every retrospective:

  1. what's going well
  2. What areas can be improved
  3. What should we be doing differently?

A retrospective is usually limited to 2 hours and is based on brainstorming solutions and committing to a solution and discussing again if success adds to the process. Retrospectives can be very effective as they take place during the development process and provide immediate feedback on the performance of the process. If used correctly, flashbacks can result in:

  • improved productivity
  • improved ability
  • improved quality
  • improved ability

Esther Derby and Diana Larsen defined a 5-step process for doing retrospectives.

Step 1: Set the stage

Setting the stage is all about setting the tone for the meeting and getting the team on board. Retrospectives work best when there is a lot of engagement and genuine feedback from the team. It is recommended that people speak up early, introducing themselves and their roles, but if team members don't change very often, this could be seen as overkill. The Scrum Master/Team Leader then sets an agenda and rules for the meeting. To increase the comfort level of team members to participate in the meeting, the team can play the following games

(Video) sprint retrospective example I sprint retrospective I sprint retrospective ideas

Check in:Round robin where people give 2 sentences about what they want from retro

Focus on/off:Get people to give feedback on every pair of words, ie. Conversation x Argument, Understanding x Defense

ESVP:Staff anonymously identify their attitude toward retrospectives as one of the following:

  • Explorers: Eager to discover new ideas
  • Buyers: look for useful information and go home with 1 idea
  • Vacationers: Not into retro but happy to be away from work
  • Prisoners: feel compelled to attend

Total scores are kept and individual votes are discarded. The team is then asked how they feel about the results.

Work agreements: small groups and create agreements, create master list

Step 2: collect the data

The next step is to collect feedback from team members about what happened during the iteration. The goal is to determine a common vision for the iteration. The team leader can use the following team-based facilitation techniques to achieve greater interaction among team members:

  1. Timeline – The team creates an iteration timeline that highlights milestones, the issues that occurred during the iteration.
  2. Triple Nickles: 5 groups get 5 minutes on 5 ideas 5 times
  3. Color-coded dots: The team uses sticky dots to show emotions where emotions were high/low during the iteration.
  4. Angry, sad, happy: The team uses color cards to describe the emotional reactions during the iteration.
  5. Find strengths: The team looks at what went well during the iteration.
  6. Satisfaction histogram: The team uses a histogram to demonstrate the satisfaction of specific parts of the iteration.
  7. Team Radar: Team assesses performance against previous process improvement goals
  8. Like: The team recalls experiences during the iteration and compares reactions to events.

Paso 3: Gere os Insights

Once the data about the iteration has been collected, it needs to be evaluated. The data can be evaluated using the followingBrainstorming Techniques:

  1. Five Whys: The team works in pairs where they analyze a problem and try to find a solution by asking "Why?" numerous times to any reason for the problem, helping to determine thePrimary cause.
  2. Fishbone Diagram Analysis: Also called an Ishikawa diagram, this is a technique used to identify the root cause demonstrated in the diagram on the left. The team draws the diagram, each branch is an area, and within that branch are the possible reasons for that branch. The diagram should have all the possible causes and the origin of the problem.
  3. Prioritize with Points: The team uses points to vote on what is important to them.
  4. Identify Themes – The team identifies recurring patterns in the data collected.

Step 4: Decide what to do

Once the data has been evaluated and the team has an idea of ​​the problems, they must decide how to fix them. A technique called "circle of questions" can be used to provide people with opportunities to provide solutions where one person chooses a problem and the next person proposes a solution.

It is very important that all the objectives created to solve a problem are SMART objectives (Specific, Measurable, Achievable, Relevant and Timely). This will help ensure that the goals can be achieved in the next iteration and can be reviewed later. To categorize issues, the team can use an action wheel where each item is categorized by simply choosing to Keep/Discard/Add or Start/More/Less.

Step 5: Close the Sprint Retrospective

The final step of the retrospective is its formal closing. The 4 tasks identified to close the retrospective are:

  1. Plus/Delta: what they want to do more and want to change
  2. Helped, Hindered, Hypothesis: Feedback on the retrospective itself, giving everyone an opportunity to provide feedback.
  3. Return on Time Spent: Level 1-5 Team Meeting
  4. Acknowledgments: Team members express appreciation for each other.

Esther Derby and Diana Larsen going through 5 stages

>> For more information, check out this PDF excerpt from the book Esther & Dianna

(Video) Sprint Retrospective - How to Run It

Mistakes to Avoid in End-of-Sprint Retrospectives

There are plenty of retrospective ideas for remote teams and free online agile retrospective tools for teams. Teams can choose online retrospective tools or they can use physical dashboards; whatever they find easy to use and enjoy. Teams should avoid:

• Think as a group and offer honest individual ideas instead.
• Be dependent on technology at all times.
• Discuss with each other, but instead do an in-depth analysis of everyone's ideas.
• Avoid negativity and focus on the goals

Instead of the whole team coming up with their ideas, individuals or small groups within the team should sit down and brainstorm. That way, the ideas will be more honest and the teams can move forward with ease.

17 of Our Favorite Agile Retrospective Examples

Happy, Sad, Crazy Retro Sprint Template

This is a template for design thinking. Instead of looking at the actual progress of the project, the model looks at the emotions of the team members. If teams are feeling burned out or burned out, the three columns can help them express their emotions and review the issues affecting them.

start, stop, continue

To beretrospective modelIt does as its name says. It allows you to outline what needs to start, what needs to stop, and what needs to continue. There are three columns for these three sections and members can use them to generate ideas.

Sailboat Retrospective Template

17 retrospective sprint examples for exciting final sprints (5)

Nosailboat retrospectivesthe sailboat, represent teams. The sailboat must lead the teams towards the objectives. Therefore, it is a good tool to assess progress at all stages of the project. Analyze the successes in terms of wind (which pushes the sailboat forward) and the goals in terms of island (where the teams must go).

He sees the anchors as challenges that hold the team back and the rocks as threats on the way. After the teams provide feedback based on this, they can scale.

retrospective starfish model

17 retrospective sprint examples for exciting final sprints (6)

This template helps you discover what team members got out of a project sprint. It is called so, thanks to the five arms of the model. This includes what to keep doing, what to do less of, what to stop doing, what to start doing, and what to do more.

Online version:The Starfish Retrospective Template | retro subway

retrospective 4L

17 retrospective sprint examples for exciting final sprints (7)

The 4L model has four quadrants where teams can enter what they liked, what they learned, what they lacked, and what they wanted. Teams can be in small groups where they can brainstorm for each of the quadrants. From the ideas that enter the quadrants, they can create a plan for moving forward.

I liked, I learned, I missed

This is a three column template. It works the same as the retrospective 4L model. In this case, you will have a column of what you liked, what you learned, and what you missed. Teams can work in small groups to brainstorm.

(Video) How to Facilitate Great Sprint retrospectives

Feedback degree

17 retrospective sprint examples for exciting final sprints (8)

A feedback grid has four sections. It is useful when project teams need to record feedback after testing the product. All positive and negative comments should be in the grid to ensure nothing is lost when the project ends. The four quadrants have the following sections: Questions, Ideas, Reviews, and Likes. Teams can fill out sections with digital sticky notes, or they can have a physical board with sticky notes.

Three Little Pigs

17 retrospective sprint examples for exciting final sprints (9)

To bemodelallows teams to identify short-, medium-, and long-term actions to complete the project. You can use it to analyze the current condition and project the future. The template is in three columns. House of Straw for things that could fall apart at any moment, House of Wands for things that need to improve, and House of Bricks for things that are stable and don't need to change.

rose, thorn, bud

The rose represents what worked and must continue. The thorn represents the challenges you have been through and the cocoon represents the opportunities and possibilities that the team has. These three sections appear in columns where you and other team members can provide feedback.

17 retrospective sprint examples for exciting final sprints (10)

I like it, I want it, what if?

If you're looking for a model of design thinking, this will give you the platform you need. You can use it to think about the next steps of the project before starting the implementation. The model is capable of turning negative feedback into constructive criticism.

working and stuck

17 retrospective sprint examples for exciting final sprints (11)

The Working & Stuck model examines what is currently working and needs to continue and what is not working (is stuck) and needs to be stopped or improved. There are only two columns in the template where you can fill in your ideas.

quick hindsight

If you are short on time and need constant project updates, you can use this template. It is a simple template with four sections. The first section discusses what was right, the second what was wrong, the third provides ideas for improvement, and the fourth is for actions to take.

anchors and engines

Anchors are things that prevent a project from progressing while drivers are things that propel a project forward. Teams should work in groups to brainstorm what is included in each column.

Mountaineer's Retrospective

17 retrospective sprint examples for exciting final sprints (13)

This is a retrospective model that requires the team to imagine themselves on top of a mountain. To get there, they needed ropes (things that helped them), they struggled with rocks (unforeseen events) and the weather (challenges), and they needed first aid (problem solutions).

Learned lessons

This is a great retro template for teams reviewing work at the end of the project. It gives teams a platform to learn lessons from the development process. Through it, teams document victories and failures and can use it when working on other projects in the future. The template has four quadrants where teams list successful, failed, planned, and unplanned activities.

Retrospective Trello Agile Templates

17 retrospective sprint examples for exciting final sprints (14)

Hot Air Balloon Retrospective

17 retrospective sprint examples for exciting final sprints (15)

This retro template works just like the retro sailboat template. With this model, teams need to see themselves floating in the air and fighting against elements like wind, hot air, sun, storms and weight. While there is no metaphor for the goal, the model helps teams analyze the challenges they may encounter along the way.

You can organize agile retrospectives in any of the following templates:

Why are agile retrospective templates important?

It is essential for all agile teams, including remote teams. It provides the time teams need to reflect and review the progress of a project. A team will also find ways to make things better. In addition to finding cheats, teams get a chance to celebrate the success and progress they've made thus far.

Other benefits thatagile retrospectiveoffers include:

(Video) New Trending sprint retrospective example I sprint retrospective I sprint retrospective ideas

  • Improved communication between team members.
  • It's time to resolve any issues between members and de-escalate issues before they escalate
  • Inform all members of any challenges and remind them of the project goals.
  • Empower agile teamsto solve problems on your own
  • Plan future actions as a team
  • Provide an opportunity for team building and energize teams.

Agile retrospective templates are ideal as they provide a simple framework for teams to gather feedback. Unlike a spreadsheet, which doesn't have a fun structure, templates are simple and easy for teams to use and remember.

Software development teams (scrum team) will benefit most from retrospective models. However, the templates work perfectly for different projects. You can do an agile retrospective after every sprint or at the end of a development project. If you have short projects (a few weeks), you can do a review after the project is complete. However, if your project lasts a few months, you may need to hold a retrospective event after a sprint.

TitleSuitable forTools neededonline version
happy, sad and crazy patternTo motivate teams when team morale is low.Physical boards or online modelhttps://retrotool.io/
start, stop, continueProject teams, performance reviews and agile sprintsonline modelshttps://retrotool.io/
I liked, I learned, I missedTo review a project when all the work is done.Online Tool https://retrotool.io/Sailboat Retrospective Agile Sprints for All Projects Online Tool https://app.conceptboard.com/board/03z7-356b-mtx8-xi28-63b6 Starfish Retrospective Agile Sprint Retrospective Can be done online or physically https://www. teamretro .com/retrospectives/The 4L RetrospectiveIntrospection at the end of a projectOnline toolshttps://www.teamretro.com/Feedback GridCollect feedback during the product testing phaseDigital stickernotes on a digital templateor a physical board and physical sticky notes thinking about projects or thinking about general projects Online Boards https://app.conceptboard.com/board/c1h5-qbq8-zb4t-dx4a-6kxpLike, Want, What If?It's an ideal retrospective template to run after a meeting or workshop, or even at the end of a project.Online template with sticky noteshttps://www.teamretro.com/
working and stuckFor when there are challenges that impede the progress of the projectOnline template or a physical whiteboard and sticky noteshttps://www.parabol.co/templates/sprint-retrospectives/working-stuck
quick hindsightQuick flashbacks and can also be used for personal reflections.online models
anchors and enginesFor agile sprints.online modelshttps://www.teamretro.com/
Mountaineer's RetrospectiveFor review at the end of a projectonline models
Learned lessonsAll teams at the end of a projectPhysical model with four quadrants
Hot Air Balloon Retrospectiveagile racingOnline tool or physical boards with sticky notes

Agile End-of-Sprint Retrospective FAQ

What do agile teams often get wrong with hindsight?

A good agile retrospective should keep the process light, so keep it simple, go ahead and let the conversation flow. What teams get wrong, however, is not the individual response time so that everyone on the team has a chance to speak.

What is a good sprint retrospective template?

A retrospective template has three to four sections or quadrants where teams enter information. In general, each retro can be linked to these 3 questions: What activities went well? What activities did not go so well? What should we continue?

Why do I need a retrospective template?

Having retrospective templates allows the team to have the quickest retrospective to set up and get direct feedback from the team. The fact that the team doesn't have to worry about the format is a sign of a great model.

How to choose a retrospective template

If members have had agile retrospectives before, they should check the previous retrospective templates for any recurring issues. The models should be stored for review at the next retrospective.

(Video) What is Sprint Retrospective Meeting? (Software Testing Interview Question #184)


What went well in sprint examples? ›

What Went Well ideas and examples in an agile environment
  • We shipped on time with no bugs reported.
  • The collaboration was great in our paired coding sessions.
  • User testing was better developed this sprint.
  • The team had a good time working together.
  • All members knew what they had to do — and did it!

What is a good sprint retrospective? ›

In fact, a good sprint retrospective idea may be to discuss how many meetings the team attends, how long meetings should last, how productive those meetings are, and how you can make meetings more productive.

What are the 3 retrospective questions? ›

Three things you can do today
  • What went well (keep doing these things)
  • What could be improved (went OK, but could be better)
  • What went badly (don't do these things again)
  • Focus for next period/sprint/month/quarter (One or two things to focus on)

What are the 4 questions for a sprint retrospective? ›

Future-oriented retro questions
  • If you could go back and change one thing about this sprint, what would it be?
  • If you could go back in time and do this sprint over, what would you NOT want to change?
  • What worked perfectly this sprint?
  • What surprised you this sprint?
  • How can we build on what went well during this sprint?

How can I make my retrospective more interesting? ›

A good retrospective is concise, engaging, and actionable. To make your retros short, facilitate only relevant discussion around specific issues and promote actionable feedback rather than abstract discussion. To make your retro engaging, set team members at ease with retro games and well-being surveys.

How do you facilitate a fun retrospective? ›

Retrospective facilitation good practices
  1. Establishing a open and honest culture in the meeting.
  2. Ensure that all team members participate in the meeting.
  3. Assure that the team establishes a shared understanding of how things went.
  4. Help the team to decide upon the vital few actions that they will take.

What are the 5 values of sprint? ›

What are the five Scrum values? The five Scrum values are commitment, focus, openness, respect, and courage.

What is an example of retrospect? ›

in retrospect

thinking now about something in the past: In retrospect, I think my marriage was doomed from the beginning. I'm sure my university days seem happier in retrospect than they really were.

What are the 5 recommended parts of the sprint retrospective meeting? ›

It has five sections, each with a specific goal.
  • Set the stage – Goal: Set the tone and direction for the retrospective.
  • Gather data – Goal: Create a shared memory; highlight pertinent information and events.
  • Generate insights – Goal: Think creatively; look for patterns, themes and connections.
Jul 13, 2014

What does a good retrospective look like? ›

The retrospective should create a safe space for people to share their honest feedback on what's going well, what could be improved, and generate a discussion around things that should change next time around—with actionable items documented.

What went well in scrum retrospective? ›

What is a What Went Well retrospective? A What Went Well retrospective helps scrum teams focus on how they felt they performed during a sprint. With just two prompts, it offers a great way of streamlining your retrospective meeting, boosting team member self-esteem, and diagnosing pain points.

What is the golden rule retrospective? ›

The Prime Directive is like the Golden Rule for agile retrospectives. The Golden Rule poses a guideline for impeccable behavior: “Do unto others as you would have them do unto you.” This simple statement leads to a safe and harmonious life in a community, assuming everyone follows this rule and is of sound character.

How do you spice up a retrospective? ›

40 ideas to spice up your retrospective
  1. Set the Stage: make sure everyone feels safe and is in in the retro.
  2. Gather The Data: what happened, make sure everyone has the same picture.
  3. Generate Insights: analyze the data to find root causes.
  4. Decide What To Do: what are experiments that could help us to improve 1% a day.
Sep 25, 2017

What are the three pillars of retrospective meeting? ›

3 Pillars of a Retrospective
  • Safe Environment.
  • Effective Facilitation.
  • Follow-up.
Aug 25, 2014

What not to discuss in the sprint retrospective? ›

The only one that I'd specifically exclude is arranging the Sprint Backlog for the next Sprint. This is a part of Sprint Planning, which would follow the Sprint Retrospective and start the next Sprint. The only one that I'd specifically exclude is arranging the Sprint Backlog for the next Sprint.

What is the common issue in sprint retrospective? ›

Inability to Capture Actions

One of the most common retrospective issues is its inability to capture actions or record and review the previous retrospective. Retrospectives are held at the end of each sprint cycle and in the general release so you can check your team's failures and successes.

What is a fun retro? ›

Fun retrospective (fun retro) – is the same scrum retrospective meeting that takes place after the sprint review but with some fun and straight-to-the-point game activities to Improve Employee Engagement and interaction between team members.

What is a starfish retrospective? ›

The Starfish retrospective is a technique developed by Patrick Kua to help teams reflect on varying degrees of actions and activities rather than simply the traditional what went well or what did not go well.

How do you make team meetings more engaging and fun? ›

For meetings that are more fun, it's helpful to invite team members to participate. To that end, make sure you send a good staff meeting agenda ahead of time. Ask for feedback on the agenda before the meeting. This sets an interactive tone even before the meeting begins.

How you can make a meeting more fun and engaging? ›

Here are 17 ideas for starting a meeting in a fun way:
  1. Do a quiz. ...
  2. Hold a meeting outside. ...
  3. Create an interactive agenda. ...
  4. Provide food. ...
  5. Make groups. ...
  6. Change the seating chart. ...
  7. Play a game of charades. ...
  8. Ask interesting questions.
Jun 24, 2022

What is fun fact retrospective? ›

Fun fact is a Retrospective tool that helps team members discover shared interests, which often leads to spending time together outside of work hours.

How do you get everyone to talk at a retrospective? ›

Start With An Icebreaker

Icebreaker questions give everyone an opportunity to speak at the start of the meeting. Sometimes getting your first word out is the hardest thing. So make it risk free by asking a fun question that helps the team open up and connect.

What is the key to a successful retrospective activity? ›

Thus, in order to make a retrospective successful, the team needs to be present with adequate preparation and effective participation. The team and stakeholders should be prepared to take corrective action at the end of each retrospective.

What are 2 examples of sprints? ›

Sprint events in track and field usually consists of the 100m, 200m and 400m race though 60m dashes are also held on occasion. The sprints are among the oldest running competitions and are said to have evolved from the 180m stadion race held during the ancient Olympic games.

What are the 3 pillars of Scrum? ›

The three pillars of empiricism at the base of the Scrum framework are:
  • transparency,
  • inspection,
  • adaptation.

What are 10 second sprints? ›

10-Second Hill Sprints

At the end of a 20- to 40-minute easy run, find a steep hill (six to eight percent grade). Run two 10-second repeats. Add one repeat per week until you reach eight. Do the first repeat at a fast but controlled pace; the rest at top speed.

What are the 5 pillars of scrum? ›

The Five Scrum Values

A team's success with scrum depends on five values: commitment, courage, focus, openness, and respect.

What are the 6 sprint stages? ›

The Design Sprint follows six phases: Understand, Define, Sketch, Decide, Prototype, and Validate.

What are the four skills in sprint? ›

Technique training for sprinting can be divided into five areas: starting, acceleration, drive phase, recovery phase, and deceleration.
  • Starting. Athletes start from a variety of positions, including stationary or moving. ...
  • Acceleration. ...
  • Drive and Recovery Phases. ...
  • Deceleration.

What are 3 synonyms for retrospect? ›

synonyms for retrospect
  • hindsight.
  • recollection.
  • reconsideration.
  • reexamination.
  • remembering.
  • remembrance.
  • reminiscence.
  • retrospection.

What is a sample sentence for retrospective? ›

Adjective They issued a retrospective report. a retrospective analysis of what went wrong The museum is having a retrospective exhibit of the artist's early works. Noun The museum is featuring a retrospective of Picasso's early works.

What is a good sentence for retrospect? ›

1. In retrospect, I think my marriage was doomed from the beginning. 2. In retrospect, it's easy to see why we were wrong.

What are the ground rules for retrospectives? ›

Ground rule # 1 – Maintain a safe and open environment. Ground rule # 2 – Respect for the opinions and perspectives of others. Ground rule #3 – Encourage active participation of all team members.

What are the 4 Ls of Agile retrospective? ›

4Ls Retrospective

The 4 Ls is a retrospective technique where team members identify what they loved, loathed, learned, and longed for in a project or sprint of work. Using this simple framework, reflect back on your work and use what you've learned to improve as a team.

How do you explain a sprint retrospective? ›

A sprint retrospective is a meeting that is held after a sprint review and before the start of the next sprint. It primarily serves as an opportunity for team members to reflect on their collaboration efforts. This is also a time for teams to identify how to apply past insights to the upcoming sprint.

How do you write a good retrospective? ›

Sample Topics
  1. Describe something another team member helped you with that you'd like to thank them for.
  2. Describe an achievement that you are proud of.
  3. Describe any questions or concerns you have about remaining work left to be done.
  4. Describe what we did well as a team.
  5. Describe what we did not do well as a team.

What do you say in a retrospective meeting from QA? ›

A retrospective is a look back at past events.
Discuss each answer as a whole.
  1. What did you like?
  2. What was lacking?
  3. What did you learn?
  4. What do you long for going forward?

What are the 5 parts of a retrospective? ›

The five stages are setting the stage, gathering data, generating insights, deciding what to do, and closing the retrospective.

What is a sample sentence example? ›

Examples of simple sentences include the following: Joe waited for the train. The train was late. Mary and Samantha took the bus.

What is an example of a sentence with for example? ›

Set "for example" off with commas.

At the beginning of the sentence: "Many animals are monogamous. For example, otters mate for life." In the middle of the sentence: "Many animals are monogamous. Otters, for example, mate for life."

What two questions are asked at a sprint retrospective meeting? ›

Valuable Retrospective Questions
  • 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?
Mar 11, 2013

What are the key elements of the sprint retrospective? ›

Here I am sharing my understanding and experience what we as a team can improve in our sprint retrospective meeting and what we should avoid.
  • Comfort level of team members. ...
  • Word matters. ...
  • Celebrate success. ...
  • Set sprint retrospective meeting goal. ...
  • Professional meeting or fun event. ...
  • Timeboxing. ...
  • Look back and see where we are.
Jan 31, 2018

How do you make a fun retrospective? ›

A good retrospective is concise, engaging, and actionable. To make your retros short, facilitate only relevant discussion around specific issues and promote actionable feedback rather than abstract discussion. To make your retro engaging, set team members at ease with retro games and well-being surveys.

How do you encourage accountability during a retrospective? ›

Accountability is about encouraging the team to think holistically about mistakes and challenges and encouraging ownership. Some techniques you can use to encourage accountability during a retrospective include: come prepared with specific challenges to discuss as a group. Turn team complaints into SMART action items.

How do you lead a successful retrospective? ›

How to conduct a project retrospective meeting
  1. Prepare the meeting. ...
  2. Welcome everyone to the meeting. ...
  3. Review the project. ...
  4. Ask the team what they learned from the project. ...
  5. Use the received feedback to make an action plan. ...
  6. Conclude the meeting and ask for additional feedback.
Feb 3, 2023


1. how to do sprint retrospective ⭐sprint retrospective explained⭐ sprint retrospective meeting example
2. how to run sprint retrospective I scrum interview questions I agile scrum interview questions
3. Agile retrospectives at Scale I How Sprint Retrospective Works I sprint retrospective explained
4. How to facilitate the best Sprint Retrospective meeting your team will love
(Your Agile Coach)
5. How I Facilitate Retrospectives
(Gareth Holebrook)
6. Retrospectives: Be Agile and Thrive
(DevOps on Azure)


Top Articles
Latest Posts
Article information

Author: Prof. Nancy Dach

Last Updated: 25/09/2023

Views: 6480

Rating: 4.7 / 5 (57 voted)

Reviews: 88% of readers found this page helpful

Author information

Name: Prof. Nancy Dach

Birthday: 1993-08-23

Address: 569 Waelchi Ports, South Blainebury, LA 11589

Phone: +9958996486049

Job: Sales Manager

Hobby: Web surfing, Scuba diving, Mountaineering, Writing, Sailing, Dance, Blacksmithing

Introduction: My name is Prof. Nancy Dach, I am a lively, joyous, courageous, lovely, tender, charming, open person who loves writing and wants to share my knowledge and understanding with you.