🛡️👽 Halo: Project Strike Team
Suit up, Spartans! Enter the battlefield of our project for a Halo-themed retro: reflect on our heroic actions, unknown threats, and tactics for future victories. Let’s make this mission a legendary success!
Template Columns
💡 Activate New Protocols
Share new strategies or tools our strike team should deploy next sprint to outmaneuver the enemy.
Base column: Start🚫 Deactivate Shields
Identify processes or habits that are weakening our defenses and should be discontinued.
Base column: Stop🟢 Recharge Overshields
Highlight effective actions or habits we should keep reinforcing for ongoing mission success.
Base column: ContinueAbout this template
The Halo: Project Strike Team retrospective uses a futuristic strike team theme to help teams reflect on what new tactics to adopt, which practices to stop, and where to double down on proven success.
When to use this template
Best used after completing challenging sprints or milestones, especially when the team needs to reassess strategies, address recurring obstacles, and reinforce resilient habits.
How to facilitate
Introduce the Halo-themed mission, emphasizing teamwork and legendary results to create engagement.
Explain each column: new strategies to activate, weak processes to deactivate, and effective actions to recharge or keep.
Give team members quiet time to independently add their thoughts to each column without interruptions.
Invite participants to review, read, and group similar items for each column to identify patterns and consensus.
Facilitate a focused discussion for each column: brainstorm specific actions for protocols to try, shields to drop, and overshields to recharge.
Prioritize the most impactful action items as a team, assigning owners and creating clear next steps.
Close by acknowledging team heroics and reinforcing the sense of a united mission going forward.
Pro Tips
Encourage creative, mission-based language to keep energy high and the Halo theme immersive throughout.
Ask quieter teammates for their 'intel' to gather diverse perspectives and avoid dominant voices controlling the conversation.
Set a clear timebox for each discussion round so energy stays high and focus sharp.
Use past sprint data or events to ground suggestions in real examples, driving practical outcomes.
FAQ
How can we keep the conversation productive and avoid going off-topic with the Halo theme?
Remind everyone the theme is a fun backdrop but keep discussion focused on concrete actions and outcomes relevant to your project.
What if participation is one-sided or dominated by a few?
Use anonymous input in the initial phase, then actively invite quieter members to share during discussion. Rotate the facilitator role if needed.
How do we ensure follow-through on new protocols?
Assign owners for each action and check in on progress during the next retrospective to build accountability.
At a glance
- Duration
45–60 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