#Agile retrospective how to#
#Agile retrospective windows#

If needed, create a legend to define what certain sticky note colors or reactions mean on the board. Write clear instructions on the whiteboard. Open a new whiteboard and select the appropriate retrospective template. Too busy to get everyone together? Run the session asynchronously Migrate work for next steps into the tracking tool of your choice to take action on and measure progress. If you would like to send a summary snapshot of the board, you can export a PNG image to share from the Settings menu. Send a message to attendees with the link to the whiteboard so everyone has access, or remind them that the board can be accessed in their own Whiteboard board picker. Keep an eye on the time to make sure that the session is on track. Use the 'Raise Hand' feature in Teams to organize the order in which participants will speak. Introduce the goal of the session and ensure that everyone is familiar with using Whiteboard.Ĭonsider how you’d like to organize the session (for example, dedicated sticky note colors for specific people, specific reactions representing different ideas, and so on).ĭuring the retrospective, encourage participation with sticky notes and reactions. Once the meeting has started, share the whiteboard from the Share tray, or send a link to the board from the Whiteboard app or from.

Share a link to the board if others are helping you prepare.Įnsure that all attendees have the Teams meeting link. In the Create panel, select Templates > Retrospective, and then choose a template.Īdd your goals for the session, and then label everything else appropriately.

#Agile retrospective windows#

You can also do this by creating a whiteboard and sharing the link in the Whiteboard Windows App or in the browser at. Navigate to the Teams meeting and select Whiteboard from the list at the top of the meeting.

#Agile retrospective how to#

How to conduct a successful retrospective sessionĭo the following: Prepare the board ahead of time There are many methods for running a retrospective. Teams are encouraged to use a variety of different methods to keep the collaboration fresh and productive. 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. Retrospectives are essential for unpacking projects and improving processes for the future, and Microsoft Whiteboard makes the process collaborative and fun!