Genre

If the last sprint was a book, what genre was it and why?

Mystery - We spent a lot of time investigating unexpected bugs
Adventure - We explored new technologies and took bold risks
Comedy - Despite challenges, we kept our sense of humor and had fun
Plot Twists

What were some of the key turning points in the last sprint?

The unexpected database issue forced us to completely rethink our approach
Discovering that user feedback contradicted our initial assumptions
When Sarah found the elegant solution to our performance problem
Key Characters

Who were the key actors from our team that you want to acknowledge?

Alex was our hero by mentoring new team members while delivering their own work
Maria played the wise sage, helping us navigate technical decisions
The dynamic duo of Pat and Sam solved our biggest blocking issue
Next Chapter

What do we want to write in to our next chapter?

Let's introduce more pair programming scenes to share knowledge
We need a stronger character arc for our documentation
Time to write in some more automated testing plot lines

What is the Book Club Retrospective?

The Book Club retrospective transforms your team's sprint review into an engaging literary journey, using storytelling elements to analyze team performance and experiences. By framing the sprint as a book, team members can explore events, challenges, and successes through a creative lens that encourages open dialogue and fresh perspectives. This format leverages familiar literary concepts like genres, plot twists, and character development to help teams reflect on their work in a more engaging and accessible way. It's particularly effective for teams who might feel stuck in conventional retrospective patterns or who want to inject creativity into their continuous improvement process. Originally inspired by the power of storytelling in organizational learning, this retrospective format helps teams identify patterns, celebrate achievements, and plan future improvements while maintaining an enjoyable and collaborative atmosphere.

Book Club Retrospective Format

Genre

If the last sprint was a book, what genre was it and why?

Encourage participants to think metaphorically about the overall tone and nature of the sprint. Different genres (thriller, comedy, drama, etc.) can reveal team sentiment and help identify patterns in how sprints are experienced.

Plot Twists

What were some of the key turning points in the last sprint?

Focus on significant events or decisions that changed the sprint's direction. These moments often reveal important learning opportunities or areas where the team showed resilience.

Key Characters

Who were the key actors from our team that you want to acknowledge?

Encourage specific examples of positive contributions while maintaining inclusivity. This is about celebrating individual contributions within the context of team success.

Next Chapter

What do we want to write in to our next chapter?

Guide the team to focus on actionable improvements while maintaining the storytelling theme. Help translate creative ideas into concrete next steps.

When to use this retrospective

  • When teams feel stuck in a rut with traditional retrospective formats and need a creative boost
  • After a complex sprint with multiple interconnected events that would benefit from a narrative approach
  • When you want to encourage more metaphorical thinking and creative problem-solving
  • To help teams that are struggling to open up about challenges in a direct way

Suggested icebreaker questions

  • If you could be any book character, who would you be and why?
  • What's your favorite plot twist from a book or movie?

Ideas and tips for your retrospective meeting

  • Start with a brief explanation of literary genres to help team members think metaphorically
  • Encourage people to build on each other's narrative elements to create a cohesive story
  • Keep a balance between creative expression and actionable insights
  • Use the storytelling format to discuss difficult topics in a less confrontational way
  • Document the 'story' to track patterns across multiple sprints
  • Consider reading out some responses in a storytelling voice to maintain the theme

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