House of Straw

Things that could easily fall apart

Our deployment checklist is just a hastily written note in Slack
We're tracking bugs in spreadsheets that nobody updates regularly
Our knowledge sharing depends entirely on one team member
House of Sticks

Things that are working but could be improved

Our code review process works but takes too long sometimes
Sprint planning is okay but we often underestimate complexity
Daily standups are useful but often run over time
House of Bricks

Things that are strong and stable

Our automated CI/CD pipeline consistently delivers quality code
Our pair programming sessions have greatly improved code quality
The team's commitment to writing unit tests is rock solid
The Big Bad Wolf

What threats or challenges are we facing?

Upcoming deadline pressure might tempt us to skip important steps
New competitor features are forcing us to rush development
Technical debt is growing faster than we can address it

What is the Three Little Pigs Retrospective?

The Three Little Pigs retrospective is a creative and engaging format that uses the classic children's story as a metaphor for evaluating team practices and processes. By categorizing feedback into houses of straw, sticks, and bricks, teams can identify weak points, areas needing reinforcement, and strong foundations in their work. This retrospective framework encourages teams to think critically about the durability and sustainability of their practices. The house of straw represents fragile or temporary solutions, the house of sticks indicates partially robust processes that need strengthening, and the house of bricks highlights solid, reliable practices worth maintaining. Originally adapted from the beloved fairy tale, this retrospective format helps teams identify varying levels of stability in their work processes while maintaining a playful, accessible approach to serious improvement discussions.

Three Little Pigs Retrospective Format

House of Straw

Things that could easily fall apart

Guide the team to identify practices, processes, or solutions that are temporary or fragile. These might be quick fixes or unstable workarounds that need more robust solutions. Encourage honest discussion about why these elements are vulnerable and what risks they pose.

House of Sticks

Things that are working but could be improved

Focus on elements that show promise but need reinforcement. These are processes or practices that have good foundations but require additional structure or refinement to become truly robust. Encourage discussion about specific improvements needed.

House of Bricks

Things that are strong and stable

Identify and celebrate the team's strongest practices and processes. These are the elements that consistently work well and provide value. Discuss what makes these successful and how similar approaches might strengthen other areas.

The Big Bad Wolf

What threats or challenges are we facing?

Help the team identify external pressures, risks, or challenges that could threaten their success. This could include market forces, technical debt, or organizational changes. Focus on constructive identification of threats rather than complaints.

When to use this retrospective

  • When you want to evaluate the stability and sustainability of your team's practices and processes
  • After experiencing failures or setbacks that highlight weak points in your system
  • During periods of growth or change when you need to ensure your foundations are solid
  • When you want to make process improvement discussions more engaging and accessible

Suggested icebreaker questions

  • If you could build a house from any material in the world, what would you choose and why?
  • What's your favorite childhood story and what lesson did it teach you?

Ideas and tips for your retrospective meeting

  • Start by explaining the metaphor clearly and how it relates to team practices
  • Encourage participants to think about long-term sustainability rather than just immediate solutions
  • Use the wolf category to address external threats constructively rather than as a complaint session
  • Consider using visual aids or storytelling elements to maintain the theme and engagement
  • Balance the serious nature of process improvement with the playful theme of the retrospective
  • Set aside time to discuss how to transform 'straw' and 'stick' items into 'brick' solutions

New to retrospectives? Read our guide on how to run a retrospective →