Skeleton Crew Retrospective

Learn from the weeks your team ran short-staffed.

Try this retrospective live

The Bones

What essentials held everything together while we were stretched?

Our automated deployment pipeline meant no one had to babysit releases manually.
Daily 10-minute standups kept us aligned even though half the team was out.
Clear on-call rotation meant incidents never fell through the cracks.
The Hauntings

What stressed us out or kept coming back to spook us?

We had a single point of failure: only one person knew how the billing system worked.
Constant context switching between tasks left me exhausted.
I was terrified something would break while our only backend dev was away.
Dead Weight

What could we drop without anyone noticing or missing it?

The weekly status report nobody actually reads.
Maintaining that legacy feature only two customers still use.
A recurring sync meeting that could easily be an async update.
Raising the Dead

What should we revive or change before the next lean stretch?

Let's cross-train at least two people on every critical system.
Create a lightweight 'lean mode' playbook for when capacity drops.
Automate the deployment checklist before the next holiday season.

What is the Skeleton Crew Retrospective?

Running with a skeleton crew means covering critical work while half the team is on leave, between hires or pulled onto other priorities. The Skeleton Crew Retrospective gives your team a slightly playful way to look back on a period when capacity was tight and only the essentials kept the lights on. It shows what really mattered, what got dropped without anyone noticing and how the team coped under pressure. The Halloween theme keeps things light around a serious topic: workload and prioritization. The board has four areas. The Bones is for the essentials that held everything together. The Hauntings covers the stress and single points of failure that kept coming back. Dead Weight is for work the team could drop for good, and Raising the Dead is where you decide what to set up or bring back before the next lean stretch. Run it after a holiday season, a hiring gap or an unexpectedly busy sprint. Finish with a few concrete actions, such as cross-training a second person on a critical system, each with an owner, so the next short-staffed period is less scary.

Skeleton Crew retrospective format

The Bones

What essentials held everything together while we were stretched?

This area is for the core structure that kept the team standing: the critical tasks, people and processes that mattered most. Ask people to name the load-bearing parts they were grateful for, so the team knows what to protect next time capacity is tight.

The Hauntings

What stressed us out or kept coming back to spook us?

Use this area for the recurring pain points and worries that haunted the team while it ran lean. Treat it as a list of ghosts to exorcise, so they don't come back next time the team is stretched.

Dead Weight

What could we drop without anyone noticing or missing it?

This area is for low-value work, ceremonies or commitments that took effort without giving much back. Ask people to be honest: running lean is a good test of what's truly essential. Capture the items the team could cut or pause for good.

Raising the Dead

What should we revive or change before the next lean stretch?

This area turns the discussion into action. Ask what the team wants to bring back, set up or improve so the next skeleton-crew period goes more smoothly. Focus on concrete actions with owners, such as cross-training, automation and a clear rule for what gets dropped first.

When to use this retrospective

  • After a holiday season or any period when much of the team was on leave and you ran on minimal staffing.
  • During a hiring gap or after departures, when the remaining team had to cover critical work.
  • After an unexpectedly busy sprint, when the team had to drop everything but the essentials.
  • When you want to find single points of failure and fix them before the next lean period.
  • As a seasonal retrospective around Halloween that still deals with a real workload problem.

Suggested icebreaker questions

  • If you were a Halloween character during our busiest week, which one would you have been and why?
  • What's the one task you'd happily bury six feet under and never deal with again?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Make it safe to talk. Running lean is stressful, so say up front that the goal is to learn, not to blame anyone for what slipped.
  • Enjoy the Halloween theme, but make sure the actions that come out of it are concrete and owned.
  • Give quieter or part-time members room to contribute. They may have covered unusual tasks and seen problems others missed.
  • Watch for survivorship bias: celebrate what worked, but dig into the hauntings and single points of failure that could bite next time.
  • Timebox each topic so you have real time left for Raising the Dead.
  • Vote on improvements so the team commits to a few changes it can deliver, not an overwhelming list.

Frequently asked questions

When should I use a Skeleton Crew Retrospective?
Use it after any period when your team ran with reduced capacity, such as a holiday season, a hiring gap or an unusually busy stretch. It shows what kept things running and what to fix before the next lean period.
How long does a Skeleton Crew Retrospective take?
Plan for 45 to 60 minutes. That leaves time to brainstorm across the four topics, group themes, vote and agree on a few actions.
How is it different from a standard sprint retrospective?
A sprint retrospective reviews the sprint as a whole. The Skeleton Crew format looks only at working with reduced capacity, so the discussion stays on single points of failure, what to drop and how to cover gaps next time.
What are the four topics in this retrospective?
The Bones (essentials that held everything together), The Hauntings (recurring stress points), Dead Weight (work to drop) and Raising the Dead (changes to make before the next lean stretch).
Is this only a Halloween retrospective?
No. The Halloween theme suits that season, but the focus on lean periods and single points of failure makes it useful any time your team is stretched thin.
Who should facilitate a Skeleton Crew Retrospective?
A Scrum Master, team lead or anyone used to facilitating can run it. What matters most is a blame-free tone, so people can talk openly about what was hard.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live