Book Club Retrospective

Tell the story of your last sprint as a book

Try this retrospective live

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 the 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

Which teammates do you want to recognize for their part in the sprint?

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 into 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 asks your team to treat the last sprint as a book. What genre was it? Where did the plot turn? Which teammates deserve a mention? Answering those questions gets people talking about the sprint as one story, including how it felt, before anyone jumps to fixes. The board has four sections. Genre captures the overall tone: a sprint that felt like a mystery or a horror story tells you something a status report won't. Plot Twists are the turning points, like a surprise requirement or the bug that changed the plan. Key Characters is where people thank the teammates who carried the sprint. Next Chapter turns all of it into what you'll do differently next time. It works well when your usual format has gone stale, or when people find it hard to talk about problems head-on. Calling a sprint a horror story is often easier than saying it went badly, and it still opens the conversation.

Book Club Retrospective Format

Genre

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

Ask people to pick a genre for the sprint as a whole and say why. The genres the team chooses tell you how the sprint felt, and the same genre coming up sprint after sprint is a pattern worth discussing.

Plot Twists

What were the turning points in the last sprint?

Look for the events or decisions that changed the sprint's direction. For each one, ask what the team learned and how it recovered.

Key Characters

Which teammates do you want to recognize for their part in the sprint?

Ask for specific examples of what someone did and why it mattered. Watch that the same few names don't fill the column, and leave room to thank whole groups too.

Next Chapter

What do we want to write into our next chapter?

Keep the story theme, but turn each idea into a concrete step. "More pair programming scenes" becomes "pair on every database change next sprint", with an owner.

When to use this retrospective

  • When your team is tired of the usual retrospective formats and wants a change
  • After a sprint full of connected events that make more sense told as a story
  • When people find it hard to raise problems directly and a metaphor gives them some distance
  • When you want to thank individual teammates as part of the retro

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?

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

Ideas and tips for your retrospective meeting

  • Give a couple of genre examples at the start so people see how loosely they can use the metaphor
  • Let people build on each other's notes so the board reads as one story
  • Use the metaphor to raise hard topics in a way that feels less confrontational
  • Make sure Next Chapter ends with real actions that someone owns, so the story leads somewhere
  • Keep a record of each sprint's genre so you can see how the story changes over several sprints
  • Read a few notes aloud in a narrator's voice if the room is up for it

Frequently asked questions

What is a Book Club retrospective?
It's a retrospective format that treats the last sprint as a book. Your team names its genre, the plot twists that changed its direction and the characters who helped, then decides what goes into the next chapter.
How do you run a Book Club retrospective?
Explain the four sections, then give everyone a few minutes to add notes privately. Talk through Genre and Plot Twists, leave time in Key Characters for thanks, then vote on the Next Chapter ideas and turn the top two or three into actions with an owner.
When should you use a Book Club retrospective?
Use it when your usual formats feel stale, or after a sprint with enough twists that it reads like a story. It also helps when people are reluctant to raise problems directly.
How long does a Book Club retrospective take?
Plan for 45–60 minutes, about the length of a normal sprint retrospective. Genre is quick, so give most of the time to Plot Twists and Next Chapter.
Can non-software teams use the Book Club retrospective?
Yes. Nothing in the four sections is specific to software, so any team that works in cycles can use it to look back on a project, a quarter or an event.

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