Retrospective

Rose, Bud, Thorn Template

The Rose, Bud, Thorn template is a structured method for team reflection and feedback, designed to help teams identify positive aspects, potential opportunities, and challenges within a project or situation. One key benefit of using this template is its ability to promote balanced feedback and productive discussions, which can lead to improved team processes and outcomes.

Sticky Note Packs Template

Use Miro’s Stickies Packs template to facilitate your brainstorming and group sessions. Use them to organize your ideas, collaborate as a team, and encourage participation from everyone involved.

RAID Log Template

Use the RAID Log template to better understand potential risks, assumptions, issues, and dependencies relating to an upcoming project. With this information, you can make effective contingency plans and prepare your resources accordingly. You’ll know what could go wrong throughout the project and how to fix the problem.

Dot Voting Template

Dot voting, also known as “sticker voting,” “dotmocracy,” or “voting with dots”, allows teams to point out issues in a series of potential solutions or to prioritize tasks when presented with various options. Dot voting is different from the default “one-share” or “one-vote” rule. Instead, each person in the group is given as many votes (or “points”) as can be filled. Those votes can either all be cast for one idea, or distributed among many ideas. You can use dot voting any time your team prioritizes options or agrees on a direction to take for a high-stakes project.

Change Control Process Template

You can predict, research, and plan for every detail of a project to go a certain way—then along comes the unforeseen and modifications are needed. That’s when a change control process comes into play. It helps define the right steps to take, gives stakeholders full visibility, and reduces the chances of errors and disruption. And this template is easy to use and highly effective—for ensuring that proposed changes are reviewed before they’re implemented, and empowering teams to veto changes that might prove unnecessary or disruptive.