Sprint retrospective template7/4/2023 ![]() ![]() The more the team evaluates their processes and acts on the improvements that need to be made, the better the output. ![]() Set a cadence for conducting regular retrospectives within your team. ![]() When this kind of feedback comes up in project retrospectives, it’s time for the team to address these challenges and work together to find the best solutions. There is always something behind the scenes that can cause people tension, and not every process may be working as efficiently as intended. While it’s easy to get caught up in the work and focusing on completing tasks, we sometimes forget to address how we get the work done. ![]() Encourage your team to get candid and ask probing questions to get the root causes. What went well? What didn’t go so well? What can we improve? Retrospectives should provide an opportunity for everyone to use the whiteboard to share their opinions. Teams can provide candid feedbackĪ retrospective meeting invites all members of the team to share their insights at the conclusion of the milestone. Retrospectives are often seen as just another meeting on the calendar, but they are worth the time and effort for a few reasons: 1. Why are retrospectives so important for a team? Reactions to allow everyone’s opinion to be heardĬolorful sticky notes to organize feedback into categories Templates for a variety of retrospective formats When planning, projects, sprints, or any other important milestones conclude, holding a retrospective is the best way to pull out key insights into what went well, while also uncovering what could be improved next time. 3, 5, etc.) they can use to pick their favorite topic(s) to discuss when everybody’s done, sort by most to least voted and start from the most popular card.Retrospectives are essential for unpacking projects and improving processes for the future, and Microsoft Whiteboard makes the process collaborative and fun! Give each participant a specific number of votes (e.g. Use voting in Trello if you are a larger team or have over 30 cards this can easily happen if your retro comes at the end of a particularly large or complex project, or you are reviewing 2-3 weeks’ worth of material. Tackle the cards in order, one by one, if you are a small team or have fewer than 20-30 cards Which card(s) do you start from? The approach depends on team size and number of cards: Some teams prefer to begin their retro by celebrating the positives first our CSMs often start from the ‘things that went wrong’ column, since that’s where they find the most valuable/useful talking points. Which column do you start from? It depends on your team’s preference. When all ideas are written, one of the team members shares their screen so everybody can see and be on the (literal) same page, and the reviewing session can begin. We created a copy of our retrospective template with instructions, so you can take it and start using it as your own right now: Make sure nothing that worked, or didn’t, goes unnoticedĬreate a list of action points and fixes to tackle week after week, so you can continuously improve Have a structured and efficient way to reflect on past activities This method works well when you and your team need to: The 3-column template requires all retro participants to list and share their ideas on what went well and what did not go well during the previous work iteration (for example the previous week), discuss and share feedback, and agree on what actions need to be taken moving forward. How to create and implement the 3-column retrospective template Discuss and assign follow-up actions (30 minutes)įinal thoughts & your copy of the template Organize and vote on the ideas (5 minutes)ģ. Start the retrospective by gathering data (5-10 minutes)Ģ. THE RETROSPECTIVE BOARD OUR CSM TEAM USE Table of contentsġ. One of our best templates for a no-frills, effective, and fast retro is the 3-column Trello board that our Customer Success Managers (CSMs) use, so we’re sharing their template and explaining how it works. Within Hotjar, different departments use different retro templates and methods depending on team size, project scope, and tool of choice. As distributed teams, we need to work hard for retros to stay an efficient and valuable use of our time we also need to make sure that everybody gets the chance to participate and share in the learning experience. Retrospectives, like team meetings in general, come with problems-and that’s also very true when you are part of a remote company like ours. What Agile teams often get wrong with the retrospective Retrospectives allow Agile teams to move quickly without losing the feedback loop and honest reflection that are needed to continue iterating at a rapid pace. In Agile, a retrospective (or 'retro') is an efficient meeting that project teams hold after completing a crucial stage of a project. ![]()
0 Comments
Leave a Reply. |