Sailboat team retrospective2/4/2024 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. One way to do this is to add ‘what works’ to a wiki-based handbook for new members who join the team.Everyone understands the importance of a Sprint Retrospective, yet as our teams become more distributed, it becomes even harder to run one successfully. But don’t forget to talk as much about what is going well as what isn’t. ‘mitigating actions’ for the ANCHOR stickies, or ‘preventative measures’ for the SHARK stickies. You could talk with the team about next steps - e.g. Once you’ve done all of this, it’s up to you what to do next. Go round each person asking what they notice or would like to call attention to. Talk about what you’ve all added to the template.When the rate of new sticky notes slows, give everyone 30 seconds longer.Spend some time ‘silent Jamboarding’ where everyone can place as many sticky notes on the template as they wish.Ensure that everyone knows how to use Jamboard by going through the basic controls.Create your own copy of the template and invite all members of your team to edit.Also, ANCHOR is about current problems, and SHARK is to do with future problems for the project or team. If it helps, consider WIND to be things internal to the project or team and SUN to be things external to it. For example, the difference between WIND and SUN in this retro and the difference between ANCHOR and SHARK. SHARK - what’s an upcoming threat to the project or team that you need to keep an eye on? what’s circling around that no-one is talking about?.SUN - what acts like sunlight for the project or team? what kind of recognition have you received? what is making you feel good?.ANCHOR - what’s dragging things down? what’s slowing down the progress of the project or team? which burdens need to be addressed?.WIND - what’s the wind in the project or team’s sails? what’s gone, or is going well? what kind of support are you getting?.LAND - what’s your destination? where are you headed? what does success look like for the project or team?. With that in mind, let’s identify the main areas of the template: The thing to remember about this process is that the way that you carry out the planning using this canvas is as important as the outcome. Goals: define what has gone well and could be improved
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |