🦘🌳 Bush Bash Expedition
Gear up, explorers! Trek through the wilds of our project, spotting hidden strengths, clearing obstacles, and plotting the trails ahead. Let’s make our journey through the bush even more rewarding together!
Template Columns
🌱 New Tracks to Blaze
Suggest new strategies or habits we should start on our agile bushwalk.
Base column: Start🪓 Clear the Deadwood
Call out practices or blockers we need to stop to smooth our path.
Base column: Stop🔥 Campfires to Keep Burning
Highlight what’s working well and should continue to light our way.
Base column: ContinueAbout this template
The Bush Bash Expedition retrospective guides your team through exploring new ideas, removing blockers, and celebrating strengths for a rewarding project journey.
When to use this template
Use this adventure-inspired retrospective at the end of sprints, after project milestones, or when your team needs a creative approach to identify improvements and leverage wins.
How to facilitate
Welcome the team and briefly explain the Bush Bash Expedition theme to set a playful, exploratory tone
Clarify each column: new tracks are innovative actions, clearing deadwood means removing obstacles, and campfires represent successful practices to keep
Give everyone 5–7 minutes to individually reflect and add notes under each column, encouraging wild ideas and honest blockers
Invite team members to review and group similar notes in each column, then collaboratively discuss the most impactful items
Facilitate discussion around each column, asking follow-up questions to dig deeper and ensure every voice is heard
Work together to select specific actions or experiments to try next sprint based on the findings
Summarize commitments and appoint owners for each action item, then close with a positive group reflection
Pro Tips
Encourage stories or examples to bring each point to life and make them actionable
Use the adventure theme to lighten the mood during difficult topics and keep engagement high
Set a visible timer for each step to maintain momentum and energy
Mix up how notes are collected, e.g., silent writing, breakout rooms, or collaborative map visuals
FAQ
What should I do if some team members are hesitant to share blockers?
Normalize vulnerability by sharing your own examples first and framing blockers as things to improve together, not as individual shortcomings.
How do I help the team choose new strategies to start?
Encourage prioritizing ideas that align with current goals and have owners willing to try them, rather than aiming for perfection or consensus on everything.
What if the same campfires come up every retro?
Acknowledge recurring strengths, but ask how they can be amplified or shared across other teams to maintain value.
At a glance
- Duration
40–50 min
- Team Size
4-10 people
- Columns
3 columns
- Base Format
Start, Stop, Continue
Tags
Ready to get started?
Use this template to run your next retrospective