4Ps Retrospective
The 4 Ps retrospective is a team activity at the end of a sprint designed to understand what worked, what didn’t, and what can be improved.
The 4Ps stand for positive, poor, potential and progress.
POSITIVE - What were our positives?
POOR - What went poorly?
POTENTIAL - Where do we have potential to improve?
PROGRESS - How do we make further progress?
This template was created by Dave Westgarth.
Get started with this template right now.
Daily Stand-up Meeting Template
Works best for:
Agile Methodology, Meetings, Software Development
The entire team meets to review the day before and discuss the day ahead. These daily meetings, also known as “scrums,” are brief but powerful — they identify roadblocks, give each team member a voice, foster collaboration, keep progress on track, and ultimately keep teams working together effectively. This template makes it so easy for you to plan daily standups for your sprint team. It all starts with picking a date and time, creating an agenda, and sticking with the same format throughout the sprint.
Reflection Island: End of Year Team Retro
Works best for:
Retrospectives, Agile Methodology, Meetings
The Reflection Island: End of Year Team Retro template offers a creative and themed approach to retrospectives, perfect for wrapping up the year. It provides elements for reflecting on achievements, challenges, and goals using a tropical island theme. This template enables teams to celebrate successes, learn from setbacks, and set intentions for the upcoming year in a relaxed and enjoyable atmosphere. By promoting reflection and celebration, the Reflection Island: End of Year Team Retro empowers teams to strengthen bonds, boost morale, and start the new year with renewed energy and focus effectively.
PI Planning Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
PI planning stands for “program increment planning.” Part of a Scaled Agile Framework (SAFe), PI Planning helps teams strategize toward a shared vision. In a typical PI planning session, teams get together to review a program backlog, align cross-functionally, and decide on the next steps. Many teams carry out a PI planning event every 8 to 12 weeks, but you can customize your planning schedule to fit your needs. Use PI planning to break down features, identify risks, find dependencies, and decide which stories you’re going to develop.
Johari Window Model
Works best for:
Leadership, Meetings, Retrospectives
Understanding — it’s the key to trusting others better and yourself better as well. Built on that idea, a Johari Window is a framework designed to enhance team understanding by getting participants to fill in four quadrants, each of which reveals something they might not know about themselves or about others. Use this template to conduct a Johari Window exercise when you’re experiencing organizational growth, to deepen cross-functional or intra-team connections, help employees communicate better, and cultivate empathy.
Midnight Sailboat Retrospective
Works best for:
Retrospectives, Meetings, Agile Methodology
The Midnight Sailboat Retrospective template offers a metaphorical journey through past experiences and future aspirations, likening the retrospective process to a midnight sailboat voyage. It provides elements for reflecting on challenges faced, lessons learned, and goals for the future. This template enables teams to navigate uncertainties, chart a course for success, and foster a culture of resilience. By promoting reflection and metaphorical thinking, the Midnight Sailboat Retrospective empowers teams to overcome obstacles, embrace change, and sail towards their goals effectively.
Reverse Brainstorming Template
Works best for:
Ideation, Brainstorming, Team Meetings
Reverse brainstorming is a technique that prompts a group to think of problems, rather than solutions. Because we naturally think of problems, it’s a great way to get a group to anticipate problems that may occur during a project. To engage in reverse brainstorming, start by identifying the problem, and then think of things that might exacerbate it. Ask your team to generate ideas around ways in which the problem could get worse. Reverse the problems into solutions again, and then evaluate your ideas.