💾🔧 Epic Computer Upgrade
Power up your team's performance in this tech-savvy retro! Let's debug bottlenecks, install fresh ideas, and keep the best processes running for a high-speed sprint.
Template Columns
⚡ Install New Features (Start)
Suggest new actions, tools, or habits we should begin implementing to supercharge our teamwork.
Base column: Start🗑️ Uninstall Bugs (Stop)
Identify practices or obstacles we should remove, just like deleting outdated programs.
Base column: Stopđź’» Keep Running Smoothly (Continue)
Highlight the proven processes and habits we should preserve for optimal team performance.
Base column: ContinueAbout this template
The Epic Computer Upgrade retrospective uses a tech-upgrade metaphor to help teams identify practices to start, stop, and continue for better performance. It's an energizing, action-oriented format that encourages creative problem-solving and sustained improvement.
When to use this template
Use this template at the end of a sprint or project to troubleshoot issues, encourage fresh thinking, and reinforce high-performing habits, especially with technically minded teams.
How to facilitate
Kick off with a fun introduction, explaining the computer upgrade analogy and aligning everyone on the retrospective’s goals.
Set a timer for silent brainstorming in each column, starting with Install New Features—encourage ideas for new actions, tools, or routines.
Move to Uninstall Bugs and prompt the team to flag any blockers, inefficiencies, or outdated practices to stop.
In Keep Running Smoothly, ask participants to highlight processes and habits the team should keep and even optimize further.
Invite team members to share and discuss their notes in each column, grouping similar items to spot key themes.
Prioritize the most impactful actions to take forward, making sure every point has an owner or follow-up plan.
Close with a round of appreciation or reflections to reinforce a positive, collaborative spirit.
Pro Tips
Use relatable tech analogies or visuals to make the session more engaging and reduce retros fatigue.
Encourage concise entries to keep the discussion focused and actionable.
Before voting or deciding on actions, check for dependencies between 'start', 'stop', and 'continue' ideas—sometimes changing one practice impacts the others.
Celebrate any previously 'installed features' from past retros that are now running smoothly; it reinforces progress.
FAQ
What if the team is not technically inclined?
The computer upgrade metaphor is flexible—explain each column’s intent in plain terms or adapt the language to fit your team's comfort.
How do we prevent the session from getting repetitive?
Bring in themed prompts or rotate facilitation styles. Highlight specific areas (tools, meetings, code, documentation) each retrospective for fresh focus.
How do we ensure action items are actually followed up?
Assign clear owners and due dates for each important action, and revisit past actions at the start of each new retrospective.
At a glance
- Duration
30–45 min
- Team Size
3-10 people
- Columns
3 columns
- Base Format
Start, Stop, Continue
Tags
Ready to get started?
Use this template to run your next retrospective