ππ¨οΈ Pressbooks Publishing Party
Turn the pages of our sprint like a lively pressroomβcelebrate the best chapters, spot the misprints, and edit for the next bestseller!
Template Columns
πβ¨ Chapter Highlights
Celebrate the successes that made our story shine this sprint.
Base column: What Went Wellπβ οΈ Plot Twists
Identify the misprints and hiccups that disrupted our narrative.
Base column: What Went Wrongπ οΈπ Editing Room
Pinpoint edits and new ideas to refine our next edition.
Base column: What We Want to ImproveAbout this template
A sprint retrospective that frames successes, challenges, and improvements as chapters of a book, encouraging storytelling and collaborative editing.
When to use this template
Use when the team enjoys creative metaphors and wants a narrativeβfocused review of their work, especially after contentβheavy sprints.
How to facilitate
Set the stage by reminding the team that the sprint is a story and each column represents a part of the publishing process
Ask participants to write individual notes on virtual sticky notes for Chapter Highlights, focusing on moments that felt like bestβselling chapters
Collect the notes, group similar highlights together, and discuss the impact of each highlighted chapter
Repeat the process for Plot Twists, encouraging candid sharing of misprints, blockers, and unexpected twists, then cluster and prioritize the most critical issues
Move to the Editing Room column, have the team brainstorm concrete edits, experiments, or new ideas, then vote on the top three actions to implement in the next sprint
Pro Tips
Use a shared digital whiteboard with a bookβcover theme to reinforce the publishing metaphor and keep energy high
Limit each sticky note to one sentence to keep contributions concise and make clustering easier
Assign a βcopy editorβ role to capture the agreed actions verbatim, ensuring clarity for the next sprint
FAQ
What if the team struggles to come up with βchapterβ language?
Encourage them to think of any completed work as a story element; you can provide examples like βlaunch episodeβ or βfeature chapterβ to spark ideas.
How do we keep the discussion from turning into a simple list of bugs?
Focus the Plot Twists column on narrative impact rather than technical detail, and ask participants to describe how each issue affected the storyβs flow.
What if we have more than three action items?
Vote for the top three using dot voting or emoji reactions, and place the remaining ideas in a backlog for future consideration.
Want a custom template?
Create a retrospective template tailored to your team's needs with our AI-powered generator
At a glance
- Duration
45β60 min
- Team Size
4-12 people
- Columns
3 columns
- Base Format
What Went Well, What Went Wrong, What We Want to Improve
Tags
Ready to get started?
Use this template to run your next retrospective