The Master Baker Template (Free)

What is the Master Baker Retrospective?

The Master Baker retrospective looks at how your team spent its time. Like a baker checking a tray, you sort the sprint's activities into three columns: Under-baked for work that didn't get enough time, Perfectly Baked for work that got about the right amount, and Overbaked for work that took more time than it was worth. It's a simple lens, and it surfaces things a standard retro can miss. Nobody files a complaint about a meeting running long or a review being rushed, but once those activities are on the board, the pattern is hard to ignore: code reviews squeezed, refinement sessions going in circles, documentation pushed to the bottom of the list. Use it when the team feels busy but not productive, or when you suspect some work is getting too much attention and other work too little. The conversation ends with specific changes to how you'll split your time next sprint.

Master Baker Retrospective Format

Under-baked What did we not spend enough time on?: This column is for work that needed more time than it got. Ask about things that were rushed and things that were skipped entirely, and look for specific examples, like a review that missed a bug, over general complaints.
Perfectly Baked What did we spend just enough time on?: Name the activities where the time spent felt right. Ask what made them work, such as a clear agenda or a timebox, so the team can repeat it elsewhere.
Overbaked What did we spend too much time on?: Find the activities that took more time or energy than they were worth. Keep the conversation on fixes, like shorter meetings or a clear way to make decisions, so it doesn't turn into a list of complaints.

When to use this retrospective

When the team wants to look at how it splits its time across different activities
After a project phase, to check whether time went where it was needed
When you suspect some work is getting too much attention and other work too little
During a heavy workload, when the team has to decide what to cut back

Ideas and tips for your retrospective meeting

Ask for specific examples. "Meetings ran long" is hard to act on, while "the release meeting ran 40 minutes over" points to a fix
Timebox each column. Running over in a retro about time is hard to defend
Keep a parking lot for improvement ideas that come up mid-discussion
Look for patterns that repeat every sprint and set aside the one-off incidents
End with one or two specific changes to how the team will split its time next sprint
Use rough relative sizes, such as small, medium and large, to compare how much time each activity took

Frequently asked questions

What is the Master Baker retrospective?

It's a three-column retrospective about time and effort. Your team sorts activities into Under-baked (not enough time), Perfectly Baked (about right) and Overbaked (too much time), then decides what to change.

How do you run a Master Baker retrospective?

Give everyone a few minutes to add activities privately to the three columns. Group similar notes, vote on the ones that matter most, and turn the top Under-baked and Overbaked items into changes for next sprint.

When should you use the Master Baker retrospective?

Use it when the team feels stretched, when a project phase has finished, or when some work seems to get too much or too little attention.

How is the Master Baker different from Start Stop Continue?

Start Stop Continue sorts behaviors into what to begin, end and keep. The Master Baker looks only at time, so it's the better fit when the problem is where the team's effort goes.

How long does the Master Baker retrospective take?

With three columns, it fits easily in 45–60 minutes.

What is the Master Baker Retrospective?

Master Baker Retrospective Format

Under-baked

Perfectly Baked

Overbaked

When to use this retrospective

Suggested icebreaker questions

Ideas and tips for your retrospective meeting

Frequently asked questions

Related templates