The retrospective is a critical part of the agile process, providing an outlet for teams to discuss how they can improve. A sprint retrospective comes at the end of each sprint and offers the team an opportunity to assess their processes.

What went well? What didn’t go so well? What does the team need to do to improve next time? Agile is all about learning and iterating. Every time you complete a sprint, there are lessons to be learned. Agile continually takes what a team learns — the good, the bad, and the bland — and turns those experiences into actionable improvements.

This post will dig into sprint retrospectives, including the benefits, how they fit within the Scrum process, how to run an effective sprint retrospective meeting, and common mistakes to avoid.

The purpose of the sprint retrospective

The sprint retrospective is a dedicated time for team discussion. The time is allotted at the end of each sprint so that all team members can examine what went well and what needs to change. It’s all part of the greater agile methodology of continually improving your processes as you learn more. There’s no one set way of doing things, and there’s always room to become more efficient and effective.

A sprint retrospective:

• Encourages a continuous improvement mindset
• Creates a safe space for sharing positive and constructive feedback
• Gives everyone on the team an opportunity to express thoughts, ideas, and experiences
• Provides feedback in real-time after each sprint
• Brings the team together around common goals
• Exposes any issues from the previous sprint that are holding the team back
• Informs leadership of success and potential roadblocks
• Helps product owners make decisions for the next sprint planning
• Sets the team on a positive path for moving into the next sprint

How the sprint retrospective fits within the Scrum process

The type of retrospective you hold depends on the type of sprint or agile methodology your team practices. One of the most common methodologies in software development is the Scrum framework.

A Scrum team has three types of roles:

• Product Owner
• Scrum Master
• Development team

At the beginning of each Scrum, the product owner decides which items from the overall product backlog are moved to the sprint backlog to be completed over the upcoming 2-4 week sprint. The exact sprint timeframe is set in advance.

The Scrum is made up of four distinct ceremonies or events:

• Sprint planning
• Daily Scrum or stand-ups
• Sprint review
• Sprint retrospective

After planning is complete and the team knows which backlog items they are going to tackle for the current sprint, the work begins. The team checks in throughout the sprint via a daily scrum or stand-up meeting. This quick but essential check-in allows the Scrum team to discuss their progress and address any potential roadblocks on a daily basis.

The sprint review meeting takes place at the end of the sprint; it’s an opportunity for Scrum team members to showcase the work accomplished during the sprint. This could be an internal presentation or a more formal demo to stakeholders.

Last comes the incredibly important Scrum retrospective. During this time, the team can discuss what went well and what could be improved so the upcoming sprint can run more efficiently. Anything that’s learned along the way or discovered in the retrospective is brought into the next sprint planning session. This Scrum process repeats until there are no more product backlog items or the product is complete.

How to run an effective sprint retrospective meeting

The retrospective is a critical part of the agile process that should be treated with care and respect. Go in with a plan. Winging it might get you by, but everyone will get more out of the process if the person or people leading the retrospective is prepared.

Use our strategies below to run effective retrospectives that everyone looks forward to.

1. Ensure everyone’s voice is heard

The loudest voices in a sprint retrospective often get the most attention and speaking time, but they don’t necessarily have better insights than anyone else. Each person involved in the sprint process should be given an opportunity to speak.

If you find a few people are dominating the conversation or that some people never contribute, switch up your strategy to include everyone. Go around the room one by one with a question that each person needs to answer, such as “What do you think went well in this sprint?” or “What was your biggest challenge?”

2. Start, stop, continue

The 'Start, Stop, Continue' retrospective format can be expressed in many forms, but the general practice is the same. At the end of a sprint, you decide what you want to start doing, what you want to stop doing, and what you want to continue doing as you move into your next sprint. It’s a simple format that covers both what went well and what didn’t go so well.

Other versions of this exercise include the Rose Bud Thorn exercise, where participants share something positive, a budding opportunity, and a negative to improve upon. There’s also the Anchors and Sails exercise, where participants share what put wind in their sails (went well) and what anchored them down.

3. Establish specific action items

The retrospective is a waste of time if you don’t leave with specific action items. What is your team going to do about the issues brought up in the meeting? Ensure you keep track of the issues and the positive feedback people provide so that you can turn them into actionable tasks or goals before the meeting is complete.

You can’t implement absolutely every change that is brought up, but the discussion should give you a place to start. Work with the team to figure out what changes will provide the most impact. You can use an impact effort matrix or similar agile tools to make informed choices.

4. Retrospective the retrospective

Every now and again, take the time to review your retrospective. Ask for feedback from all team members on how the process could improve. What would make the experience easier on the team? What would they like to see implemented? What hasn’t been working during your recurring retros?

Wow, that’s getting a little meta, but it’s an important step. You need to continually assess your retrospective as well to make sure you’re getting the most out of the experience.

One thing to watch for: When people are bored, they engage less, which means it’s important to switch things up. You don’t want your retrospective process to run stagnant or lose its effectiveness.

5. Review action items at the next sprint retrospective

Make sure the hard work of your retrospective pays off. At the beginning of the next retrospective, take a small bit of time to review your previous action items. What goals and action items did you leave the last retrospective with? Did you accomplish what you set out to do, or do you still need to work at it?

Common retrospective mistakes to avoid

Avoid these common mistakes when running sprint retrospective meetings:

❌ Allowing a few people to dominate the conversation

❌ Not empowering softer voices

❌ Jumping to conclusions without a thorough discussion

❌ Asking the same questions over and over without mixing things up

❌ Forgetting about or not implementing the action items of the previous retrospective

❌ Skipping a retrospective due to lack of time or resources

❌ Forgetting about stakeholder and customer needs

❌ Failing to improve upon your retrospective process

Put your retrospective ideas into action with Easy Agile TeamRhythm

Sprint retrospectives help the entire team learn from each experience and improve. Doing them effectively means evaluating the retrospective itself, empowering voices, and listening to them.

We’re passionate about putting the needs of the customer first and foremost. Easy Agile builds products specifically designed for Jira users to help agile teams work more efficiently and effectively.

Easy Agile TeamRhythm supports the work of your agile team from planning right through to retrospective, encouraging continuous improvement so you're always getting better at what you do, and delivering better for your customers.

TRY EASY AGILE TEAMRHYTHM FOR FREE

It’s time to get things done and hand over the project to the programmers. But before they get their hands dirty, someone must plan the Scrum sprint or iteration. The Sprint Planning meeting is one of Scrum’s ceremonies, and it's the sprint's opening event. 🎬

Let's walk you through the event and explain how to prepare and hold one successfully. You'll also learn who participates in Sprint Planning and why the meeting is so important.

What's a Sprint Planning meeting?

Sprint Planning is a Scrum meeting. It kicks off a sprint, so it occurs on the first day of a new sprint. If applicable, it should occur after the Sprint Review and the Sprint Retrospective from the previous iteration.

Sprint Planning aims to decide the deliverables for the upcoming sprint and define a plan to develop the work.

The entire Scrum Team (the Product Owner, the Scrum Master, and the Development Team) collaborates during Sprint Planning.

Can you imagine a successful project without planning? 🙅 We can't either, so we don’t start a Scrum sprint without planning it.

To plan a Scrum sprint, you need to decide:

• The sprint's duration — remember that a sprint is a timebox
• The sprint goal, which is its purpose and represents the product increment's value to the customer
• The work that the Development Team can complete during the sprint, what work items the team should do first to achieve the sprint goal, and how long they should take considering the team's capacity

Additionally, Sprint Planning should motivate the team and set realistic expectations.

By the end of the Sprint Planning meeting, the team must produce the following outcomes:

• A shared understanding of the sprint goal. This goal is the guideline for evaluating the Development Team's work once the sprint is over.
• The Sprint Backlog. This artifact represents the conversation between the Development Team and the Product Owner on the to-do work. It's the result of a balance between customer value and development effort.

Now, each Sprint Planning meeting requires some preparation. Read on about who should do it and what it entails.

How do you prepare for Sprint Planning?

The Product Owner should follow these steps to set the foundation for successful Sprint Planning:

• Combine the output of the previous Sprint Review, feedback from stakeholders such as management and customers, and the product vision
• Update and, if necessary, refine the product backlog
• Know the customer value that the development team needs to create in an increment

So, once all the preparation is over, it's time for the Sprint Planning meeting to take place.

How should the meeting go?

1. The Product Owner indicates the Product Backlog items — and corresponding priorities — that they consider the next sprint's best candidates. Items can be user stories, tasks, or bugs. The Product Owner proposes those items according to customer value and product vision.
2. Based on effort estimates and the Product Owner's proposal, the development team selects the product backlog items to work on during the current sprint. By promoting those items to sprint backlog items, developers agree on the sprint goal with the Product Owner.
3. Although optional, the team might discuss dependencies between items and who should work on each one of them.

Very few steps, right? However, some practical actions should add on to these steps. Discover what those actions are below.

How do you execute a successful Sprint Planning meeting?

1. Limit the meeting's duration. ⏳ Sprint Planning shouldn't take longer than 1-2 hours per sprint week. That means the meeting shouldn't take more than 2-4 hours for a two-week sprint.

2. Let the Scrum Master be the guardian of time. They're the ones responsible for ensuring that the meeting happens within the defined timebox.

3. Hold the meeting on the same day and at the same time every time. 📅 Team members can be quite busy and have full agendas. That's why reserving a slot in every participant's agenda is a good practice.

4. Define valuable, clear outcomes. 🎁 Those, together with a clear sprint backlog, increase the Development Team's motivation. Producing the right outcomes is pure satisfaction, and a clear work plan is the recipe to achieve that.

5. Make sure that the Scrum Master guarantees these things. First, that the conversation between the Development Team and the Product Owner is fruitful. They should all agree on the sprint goal. Second, that the developers make good choices when moving product backlog items to the sprint backlog. Selecting an item that is feasible for the sprint duration, team capacity, and workload is a good choice.

It might seem easy, but this is not all there is to do during Sprint Planning. There's a bunch of things to avoid.

If we were to give you some advice...

Make effort estimates against the development team's capacity. To decide on the amount of work that the team can accomplish in a sprint, consider the team's capacity. (And remember, estimates are just that — estimates.) Developers consider their previous experience, yet each sprint is unique and might change over its course. However, considering team capacity improves the accuracy of effort estimation. Additionally, story points might help the team with effort estimation.

Consider that the development team's ability to estimate should improve over time. Therefore, the team should not critique less accurate effort estimates after the sprint. Otherwise, the team will take much longer to estimate or provide much bigger estimates next time.

Don't try to plan every single thing during Sprint Planning. Leave the idea of coming up with the most complete, perfect Sprint Backlog ever at the front door. After all, Scrum is all about flexibility, and "Better done than perfect." So, a Sprint Backlog that’s complete enough to get developers started is just what it needs to be. Remember that solving complex problems requires a learn-by-doing approach, which turns planning into an equally complex job.

Figure out a realistic expectation for the sprint's outcome. Setting unrealistic expectations for the increment that the development team can produce over a sprint is not a good idea. It might make developers frustrated that they couldn't deliver, which can seriously affect their motivation and performance. On the other hand, realistic expectations set the team for success and a sense of accomplishment. Besides, they facilitate the conversation between the developers and the Product Owner so they can agree on the sprint goal.

Have a well-refined product backlog. It must be detailed enough to allow the Development Team to understand what the work items are about. You don't want to waste precious Sprint Planning time splitting work items into a maximum of one per day. Define and follow a backlog refinement process and ensure that Product Backlog items meet your definition of ready.

Propose a clear sprint goal. 🎯 The Product Owner must be very clear on the expected customer value for the increment. Otherwise, the development team might choose a set of product backlog items that don’t relate to one another. The result could be unexpected outcomes and a low sense of accomplishment.

Clarify the definition of done with the Development Team. Knowing what work done means in the current sprint helps the developers meet the expectations. That's because they can better understand what to do to create the increment. Also, a clear definition of done makes the Development Team more confident when estimating effort.

Strong Sprint Planning makes your project stronger

If you're following the Scrum framework, Sprint Planning is not a choice. Nevertheless, if you ever feel tempted to skip it, bookmark this article and read the following. 📑

It's easier to understand the sprint goal, to-do work, and sprint outcomes with a successful Sprint Planning meeting. If the team doesn't know where it's heading and how to get there, it gets really tough to satisfy customer needs. It's equally hard to deliver your customers valuable increments if you don't organize work by priorities.

Sprint Planning is about instilling clarity and organizing work before it's too late in the iteration. It's also about involving the whole team in preparing for all the effort that a sprint demands. A note: Keep in mind that a sprint plan must fit into a sprint's timebox and consider the team capacity.

Easy Agile TeamRhythm is perfect for Sprint Planning. It's a fast, straightforward, visual, and collaborative tool that allows you to:

• Drag items directly from the product backlog onto the user story map
• Register effort estimates in user stories
• Edit story point estimates
• Prioritize user stories in each sprint by ordering them inside the respective sprint swimlane
• Analyze sprint statistics to ensure that the planned work doesn't exceed the team's capacity and the sprint goal is realistic
• Visualize what the team will deliver and when by arranging user stories into sprint swimlanes

Let us know if you have any questions about Easy Agile TeamRhythm. We highly recommend it to your Scrum project, and our customers recommend the same.

Ceremonies are regular events held by Scrum teams. ‘Agile’ is a broad word describing a different way of working with shorter, time-boxed cycles for releases.

Under the broad umbrella of agile, Scrum is one of the most popular approaches that teams use to organise their work and releases.

Each short iteration of work in Scrum is referred to as a sprint. A sprint is normally a 2 week period where the team focuses on a small slice of work.

The idea is that everyone focuses on 1 slice of work. And that slice is to be completed and shipped to the customer within that same sprint.

Scrum can be broken down into a few important elements:

1. Roles
2. Artifacts
3. Ceremonies

This post will focus on the Scrum Ceremonies.

All of the 4 Scrum ceremonies help ensure the Scrum team stay focused on the slice of work they agreed to focus on in that sprint.

It helps the team with transparency about progress on the work they committed to finish and to raise any issues early before they become blockers.

Let’s have a look at each of the four agile ceremonies in Scrum:

1. Stand up (or daily Scrum)

Goal of the stand up: a brief check-in where the team can raise issues or communicate with the whole team face to face.

Who joins the daily stand up: Developers, Scrum Master, Product Owner

Outcome of daily stand up: the team raises any blockers, but doesn’t have to solve them. Ensure each team member is clear about what they are working on. Each team member should be able to answer these three questions:

• What did I complete yesterday?
• What will I work on today?
• Am I blocked by anything?

When to hold a stand up: daily

Tip: stand ups can be done by business teams and don’t always have to be face-to-face. Here’s a photo of Australian bank ANZ’s executive stand up in action:

And another pic from InsideIT’s stand up:

2. Sprint Planning

Goal of sprint planning: sprint planning helps the team prepare for what work is coming up next. The team discusses each item of work which has been prioritised by the Product Owner.

Who does sprint planning: Developers, Product Owner, Scrum Master

Outcome of sprint planning: that everyone knows what the sprint goal is and how they are going to achieve it. Make sure everyone understands what’s the overall vision or objective of the work.

The team will be comfortable with what work is available to be picked up in the next sprint. The team will discuss any impediments or opportunities and how they can optimise the way the work will be completed.

The team will also estimate the work and draw a line when it is estimated that the effort to complete the work exceeds the team’s capacity or historical velocity.

When to hold sprint planning: at the end of a sprint or very beginning of a new sprint.

Bonus: sometimes in sprint planning you will find things you won’t do, and that’s valuable too.

3. Sprint review

Goal of the sprint review: showcase the work completed and receive feedback from the Product Owner and relevant stakeholders.

Who joins the sprint review: Executive Sponsors, Developers, Scrum Master, Product Owner

Outcome of the sprint review: each team member feels empowered by showcasing their work to the team. The team can celebrate their achievements. Executive team can ask questions. Product owner can provide feedback and check the work is of high quality and satisfies the user story. Works best with drinks and cake.

When to hold a sprint review: at the end of each sprint.

4. Retrospective

Goal of the retrospective: honest discussion about what worked well and didn’t work well. Encourage self-improvement and transparency.

Who joins the retrospective: Developers, Scrum Master, Product Owner

Outcome of a retrospective: receive feedback from the team and seek to improve in the following sprint. The beauty of agile and Scrum is the fast feedback loop.

If something isn’t working well, it only hurts the team for a maximum of 2 weeks. It can then be addressed at the retrospective and action can be taken to address the issue before it gets out of hand.

The outcome should be a commitment from the team to focus on addressing areas that need improvement or continuing behaviours that benefit team health and/or velocity.

When to hold a retrospective: at the beginning of a new sprint, reflecting on a sprint that has just ended.

---

The common theme across these Scrum ceremonies is that they encourage team collaboration, transparency and communication.

In my experience, this is what truly makes agile a better way of working.

It’s not the story points or even the way the backlog is prioritised that makes a difference. The true game-changer of agile is that it helps teams with open and honest communication.

These agile/Scrum ceremonies won’t always work the same for every team.

However, they are a great way to facilitate conversation and encourage continuous improvement.