1/30/2024 0 Comments Agile retrospective sailboat![]() How to run a remote retrospective in 5 steps You and your team will use the information gained during a retrospective to identify action items, implement improvements, and make your next sprint that much better. Iterate more effective sprints in the futureĪ retrospective has one key goal: to help your team become more and more effective. That level of ownership is important, especially when you consider that in one study, nine out of 10 employees pointed to accountability as one of the top development needs in their organizations. Taking a fine-tooth comb to the successes and sticking points of your previous sprints requires that your team members hold themselves accountable for their responsibilities in the process. But, having regular retrospectives on the calendar means your team prioritizes continuous improvement. They’re meant to be refined and improved, and your retrospective is a chance for your team members to identify what went well and what needs to change. That time for reflection and discussion can get lost in the hustle and bustle of your daily task list. Identify flaws and inefficiencies in your processes But, it’s a good thing that your retrospective meeting is unmissable because it offers tons of benefits. You can’t skip your retrospective, as it’s a core piece of most agile approaches. Why the retrospective is a critical part of the agile process Over 300 employees participated in Miro's remote retrospective during a virtual offsite in 2020. You’ll use video conferencing (like Zoom) and an online whiteboard to collaborate with your team. However, during a remote retrospective, you and your team members won’t be in the same room when you have this conversation. Retrospectives typically happen at the end of the sprint (hence why they’re often referred to as sprint retrospectives) and are a chance for your team to evaluate your processes, get down to root causes, and make necessary changes. What is a remote retrospective?Ī remote retrospective is a version of the agile retrospective you’re likely familiar with. Let’s talk about how your distributed team can run a successful remote retrospective. This can make your agile retrospectives particularly challenging. Buffer’s 2020 State of Remote Work Report found that communication and collaboration are some of the biggest challenges of working remotely. That offers plenty of advantages, but there are hurdles to overcome as well. ![]() More and more teams are moving away from the traditional office environment and working together online instead. Remote work is no longer the future of work – it’s the present. Start with the cluster with the most votes: Discuss the topic and define action(s).How to run a successful remote retrospective Depending on the number of groups, everyone gets 2-3 votes. Together, determine the headings for the groups.Įveryone votes for the groups. Use the "Gathering Insights and Defining Actions" frame.Ĭopy the cards from "Gathering Topics," discuss how they can be grouped, and then group them. Step 3: Getting Insights and defining Actions ![]() There may also be icebergs (impediments) that you don't expect."Įach participant writes 2-3 cards and places each card in an appropriate position in the picture.Īfterward, everyone briefly says what they wrote on the card. Some things move you forward (wind, engine, good navigation) and things that stop you (bad weather, someone has dropped anchor). Introduce the activity: "Imagine that your last sprint was a ship's voyage. Then do a short round where everyone briefly says why they chose that particular image. Have participants mark the respective boat image with a sticky note with their name. Which ship would you be right now and why?" Use the frame "Setting the Stage" for a small warm-up.Īsk participants the following: "Imagine you are a ship. The time you need depends on the team size, but please plan at least 60 minutes. The anchor / the thunderstorm: Things that stopped or hindered the team The sails, the engine, the wind: Things that helped the team to move forward ![]() The Boat: It symbolizes the individuals and the team itself The template works with metaphors around sailing: The template supports the retrospective phases “Setting the stage”, “Gathering data”, “Getting Insights”, “Defining Actions”, and “Closing”. Then, based on their reflections, actions can be defined. The team can identify what went right, what went wrong, and what impediments they are facing. The template provides a fun, interactive, and easy way for your team to reflect. The purpose of a retrospective is to inspect and adapt concerning individuals, interactions, processes, tools, and quality. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |