Under-baked

What did we not spend enough time on?

We rushed through our code review process and missed some important issues
Documentation updates kept getting pushed to the bottom of our priority list
We didn't spend enough time onboarding our new team member properly
Perfectly Baked

What did we spend just enough time on?

Our daily stand-ups were consistently focused and productive
Sprint planning meetings hit the sweet spot between thorough and efficient
We allocated just the right amount of time for pair programming sessions
Overbaked

What did we spend too much time on?

We spent too much time debating minor UI details
Our release meetings dragged on with unnecessary discussions
The feature refinement sessions kept going in circles

What is the Master Baker Retrospective?

The Master Baker retrospective uses a culinary metaphor to evaluate time management and effort allocation within teams. Drawing inspiration from the precise art of baking, this format helps teams identify activities that received too much attention, too little attention, or just the right amount of focus. Just as a master baker needs to perfectly time their creations, teams need to balance their time and resources effectively. This retrospective format encourages participants to think critically about how they're spending their collective time and energy, using familiar baking concepts to frame the discussion. This approach is particularly effective for teams struggling with time management or those looking to optimize their workflow. By categorizing activities as under-baked, perfectly baked, or overbaked, teams can easily identify areas requiring adjustment in their process.

Master Baker Retrospective Format

Under-baked

What did we not spend enough time on?

This column helps identify tasks or initiatives that need more attention. Guide the team to consider not just what was rushed, but also important matters that were overlooked entirely. Encourage specific examples rather than general statements.

Perfectly Baked

What did we spend just enough time on?

Focus on identifying successful time allocation that the team should maintain. These are practices worth preserving and potentially replicating in other areas. Help the team understand what made these activities well-balanced.

Overbaked

What did we spend too much time on?

Help the team identify activities that consumed disproportionate time or energy relative to their value. Guide discussion toward constructive solutions rather than complaints. Focus on finding efficiency opportunities.

When to use this retrospective

  • When the team needs to evaluate and optimize their time management across different activities
  • After completing a significant project phase to assess time allocation effectiveness
  • When there's a sense that some activities are getting too much or too little attention
  • During periods of high workload when prioritization becomes crucial

Suggested icebreaker questions

  • If your last sprint was a baked good, what would it be and why?
  • What's your favorite recipe for success when working on challenging projects?

Ideas and tips for your retrospective meeting

  • Encourage specific examples rather than general statements to make the discussion more actionable
  • Use timeboxing for each topic to avoid the irony of poor time management in a time management retrospective
  • Keep a parking lot for improvement ideas that arise during the discussion
  • Focus on systemic patterns rather than one-off incidents
  • End with clear, actionable items to adjust time allocation in the next sprint
  • Consider using relative sizing to compare time spent across different activities

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