The driving principle for the retrospective is that a team can always do better and should always be looking for ways to improve. Read our recent post on agile methodologies for product managers.Ĭoding architect and Agile specialist with over 20 years of experience, founder of Lerni.ioįollow him: on Twitter or LinkedIn Historically, the whole team has met in a conference room for the exercise, but today’s prevalence of distributed teams requires new solutions. This helps make the next sprint planning much easier for the scrum master/product owner/whoever is running the next sprint/scrum. Sprint retrospectives usually happen at the end of each sprint and help build a strong scrum framework through continuous improvement. In essence, it is a meeting where the previous sprint is discussed. Its goal is to allow the scrum team to reflect on the sprint and determine how they can use that knowledge to improve future sprints. What is a sprint retrospective in Agile?Ī sprint retrospective meeting, also called an Agile retrospective, is a brief exercise where scrum team members discuss what could have made the last sprint/scrum more efficient. We also complemented the guide with useful tips from Lieuwe van Brug from Lerni.io, who has practiced running retrospectives with distributed teams many times. Scrum masters are trained to perform sprint retrospectives in person with their team, but what to do if someone in your team is becoming distributed? We created this guide to show you that even if you can’t be in the same room, it’s still possible to lead a successful retrospective. ![]() We have already used it again for a workshop.Everyone understands the importance of a Sprint Retrospective, yet as our teams become more distributed, it becomes even harder to run one successfully. The toolĪbout Boardting, the stickie tool we used: the team liked it, it was easy to use (apart from the dot voting we really did not get to work like we wanted). This retro technique helps the team focus on the future they want and how they will get there. Retros can sometimes turn into nonconstructive whining meetings. ![]() I also very much appreciate the positive switch that happens when you turn the negative anchors into something positive (the goals) and decide together on a way to reach that (the actions). The team also said that the discussions we had during the retro were great, much better than in any retro they had before.Īs the facilitator I can only agree with the team, the discussions were really good. Also, having a pretty picture to look at made the retro more fun. And that the technique helped very much with that focus. They said it was nice to focus more on the big picture and what is ahead instead of introspecting on only the last sprint. The team really liked the Sailboat retro. If your team is familiar with the tool and you don’t spend time evaluating you could probably do it in 60 minutes. We also spent some time evaluating the retro and the tool. We spent some of that time explaining the Sailboat retro technique and some additional time trying out the new stickies tool. I had booked 90 minutes for this meeting and that was a good amount of time. ![]() I copied the link to the board and sent it to the team members so they could join that board. I went into Boardthing and set the boat picture as a background in a board. I found Boardthing that seemed to fulfill everything that I needed and decided to try it out. Enabled me to set a picture as a background and the team members to put stickies on it.The team members could use without having to create their own account.I had a vision of us using an online sticky tool and putting our stickies on the picture of the boat. I read about the Sailboat retrospective and really wanted to try it, but I was not sure how I could make it work with the team being distributed. I wanted to do something different, and I wanted the retro to be as much like a live meeting as possible. They used slack video call and confluence for documentation during the meeting. My team had a history of using the 4L retrospective technique every sprint for a long time. In the retrospectives we always used video since it gives a feeling of being close to each other when being distributed. We used slack for our daily communication: text communication, audio and video calls. We were distributed in 2 locations with a 7-hour time difference. I had recently started working with a new team. How do I host a retrospective that feels like a live meeting even though we are distributed? Background
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |