Our sprint retrospectives always include a “5-Star” board. We separately, then collectively, brainstorm ideas that fall in each point of the star. It’s a nice way to reflect on the good, the bad, and the ugly as we figure out our best way to move forward. 1 - What to continue 2 - What to reduce 3 - What to increase 4 - What to stop 5 - What to start Once we effectively group these ideas into the proper category and theme, we devise a game plan for next time.
Before initiating the serious meeting, encourage your team to form small discussion groups first where they would break down the points and give their suggestions first. This will allow them to get their headspace in the meeting and give them ample time to come up with ideas initially. Notice how your team will not be zoning-out during the meeting because they'll be looking forward to present their ideas and will be more engaged in discussing other members' topics.
This is a basic method that we have been practicing since primary school. First, a list of solutions is enumerated. The solutions are also a product of the brainstorming session the group has come up with. And then, the group will deduce the list until the best possible solution is presented and will be the one implemented.
We adopt the “What, So what, Now what?” or W3 sprint retrospective. It’s a fairly straightforward Liberating Structures technique that can run for 45 minutes. Groups are encouraged to reflect on a shared experience together, harmoniously. They gather facts about what happened, understand its reason or purpose, and look into action plans moving forward. What I like about this activity is that it forces teams—both leaders and their members to take time to observe and assess situations before carrying out final decisions.
I have noticed how participants view our sprint retrospective meetings (SRM) as another tedious task they have to prepare for. What we did in the recent SRM was implement a story-telling type of delivery. Employees were notified in advance about the theme and then given ample time to prepare. This is, by far, the most entertaining SRM everyone has been to. The whole team had fun analyzing stories and how they relate to their personal work experiences. Some stories were pretty straightforward, anchoring from classical short stories, while some made their own. Overall, I am confident to say that it was a huge success. Not only were the creative sides of the participants shone through, but this also served as a team-building activity in hindsight. Everyone was eager to enter the next sprint with a clear mindset, meaning the meeting served its purpose and much more.
Quick Review The team's finished work is displayed during the sprint review, and stakeholders are polled for their opinions. Attendees from a range of backgrounds provide insightful observations from many angles. Additionally, this occasion promotes confidence among internal and external stakeholders. To help your team present with confidence at the meeting, especially if external stakeholders are attending, provide time in your schedule to practice beforehand. Don't display unfinished work. If you're unsure whether the task is finished, review your sprint planning and the initial criteria.
One unique sprint retrospective ritual I participate in with my agile team is : Chronological Retrospective For retrospectives involving several teams and sprints, this approach is extremely useful. This method allows me to go back over a longer period rather than just your most recent sprint. By adding the concept of time, a timeline retrospective gives my retrospective meeting new depth. I'll reflect on significant occasions from a specific time frame, pinpoint problem areas, and create action plans to deal with those issues. Retrospectives may be interesting for young teams. For more experienced teams, though, they may become tedious. Although this method leverages several well-known retroactive notions, it does so in a novel way.
For our team's sprint retrospective ritual, we follow the Lean Coffee format that builds agenda and specific topics in a small coffee group discussion on the spot. This approach is on brand with our company and love for coffee. It allows everyone to start a topic and build upon it, go deeper into its specific details, and connect it to another area we typically don't have time for in a formal meeting. It also provides our team a venue to resolve issues and concerns while everyone is present to contribute. A cup of coffee creates a calm and relaxing environment that encourages everyone on the team to speak up. It's an excellent approach to tackling crucial elements without taking too much time and sticking to a rigid agenda.
The activity levels retrospective challenges team members to evaluate their work by identifying the greater, moderate, and tiresome elements. An agile retrospective's goal is to enhance the team's cohesiveness and individual employees' quality of work. For instance, you might find that a teammate who is eager to take over a duty you find boring finds it attractive. But you may utilize it to figure out why your team members aren't feeling motivated during retrospectives. What could inspire them even more? What causes them to be uninspiring? Activity Level is only one example of a retro that emphasizes emotions.
We have a unique sprint retrospective ritual that we call the "Plus/Delta." At the end of every sprint, we take a piece of flipchart paper and draw a large plus sign in the center. Then, we go around the room and each team member shares something that went well during the sprint (the "plus" part of the exercise). Once everyone has had a chance to share, we move on to the "delta" part of the exercise. This is where we identify areas that need improvement. We typically come up with one or two actionable items that we can work on for the next sprint. This exercise helps us to focus on continuous improvement and always be moving forward as a team. Plus, it's a fun way to end each sprint!
We use “One Word-Battery Check” as a sprint retrospective. Through sticky notes, we encourage our team members to share a word that best describes how they feel about a recently held project or meeting. We also use it to identify any issues they might have had in carrying them out. Once we get enough details, we discuss them as a group and devise ways to correct or improve initiatives moving forward.
At the end of every sprint, my agile team participates in a unique retrospective ritual. We start by going around the room and each sharing one thing that went well during the sprint and one thing that could be improved. Then, we spend a few minutes brainstorming ways to make the improvements. Once we have a list of ideas, we vote on the ones we think would be most effective. Finally, we choose one or two ideas to implement during the next sprint. This ritual has helped us to continuously improve our process and work more efficiently as a team.
One of the most important aspects of a sprint retrospective ritual is engagement. One way to get engagement is to have a laundry day. This shows everyone when items are presented clearly and which feel vague. It's perfect for a team that makes unconscious decisions without questioning. Set up a short clothesline and have 20 clothespins ready. Put up a picture of a white shirt on one side of the clothesline and one picture of dirty pants on the other. Now, tell team members to write ideas on index cards that either fall into clean and clearly understood or dirty and confusing. Have them hang the notes up on the clothesline in the appropriate areas. Have the team vote on two "clean" items and two "dirty" items for it to talk about.
Sprint Planning. After a few group discussions and conversations, you ought to have an unmistakable choice of the work that the Development Team can finish during the run toward Sprint Planning. This is known as the Sprint objective. The Sprint objective is an addition of complete work, and everybody should have positive expectations about the responsibility. The object backlog characterizes impotence that influences the work request. Then, at that point, the Scrum Master changes that choice into Sprint build-up. Tips: Concentrate on cooperation instead of rivalry. Calculate public events and any colleague's rest or outings. Break client stories into assignments to get tasks more functional for the Development Team. Assuming that there's time, allocate those undertakings during the circumstance. Remember your group's speed - a history of the time it took to execute a similar task.
Our company uses a simple framework to guide our retrospective rituals. Each team member lists things about the last sprint that made them feel mad, glad, and sad. Observations that fall under “mad” can include frustrations or inconveniences they encountered. “Sad” observations involve undesirable outcomes, and “glad” observations include results or situations that we want to celebrate and replicate. This approach work because it centers on emotions, which means that every team member can contribute with unique perspectives. It also helps build a healthy team dynamic where everyone feels safer talking about their experiences and the challenges they face.
My team does a "What Went Well, What Didn't Go Well, What Can We Improve" for every retrospective. By structuring our retros in this way, we are able to develop a narrative of our progress and setbacks that helps employees feel heard, while it also provides clear next steps for the team. Without this ritual, our retrospectives would likely devolve into a series of gripes and complaints with no real actionable items.
CEO at Live Poll for Slides
Answered 4 years ago
It is an unspoken rule in my place that every time we have a sprint prospective meeting we have to have a meal together. It is a time that the team members look forward to because they get to have a nice meal sponsored by the company. During the meal together we get to recognize and award those that have performed really well. As a CEO and part of the team that authorized the budget for this ritual, I know that this acts as motivation for continuous improvement for the team in an effort to earn the same treats the next time.
That one unique sprint retrospective ritual you partake in with your agile team starts with an icebreaker question or game. Teams only have efficient retrospectives when they face psychological safety. Teammates must feel comfortable expressing what went well and what could have gone better. A short icebreaker game or question at the beginning of your retrospective helps people to check in to the meeting and contributes to a positive and safe atmosphere. Icebreakers get everyone talking and give people a chance to speak at the beginning of your meeting, which helps them feel included.
Scrum meetings are crucial components of the agile software development process. The scrum meeting is intended for the Product Owner and Development Team to convene and evaluate the prioritised Product Backlog at the start of a new scrum sprint. The team should eventually produce a sprint backlog containing all the tasks they are committing to finish at the conclusion of the sprint through a series of talks and agreements. The sprint aim refers to this. The sprint goal should be a shippable increment of work, meaning it can be demonstrated at the end of a sprint
It's the end of the iteration. The deadline is in only a few hours and tensions are high. The commitment is on the line. Wires were crossed and tempers flared. This situation creates tension that can last long after the deadline and demo have passed. When we have this situation, we do what we call, "Clear the Air". While our retro board will inevitably have something on it relating to the flare-up, it's often masked in a thick layer of passive aggression and delivered with a patronizing tone. This only serves to make the situation worse. When we see this situation, the rest of the team can declare that the two must "Clear the air". Our first goal is to diffuse the anger and bring back lighter spirits. We have a few ways of doing this but one of my favorites is having the two wear clown noses. Other times we've gotten spray bottles and given anyone who raised their voice a spritz. The purpose is to get the "combatants" laughing. This way they can talk and "clear the air".