Given that our priorities should be a reflection of our actions and time spent, this sprint retrospective template idea gives your team a valuable mechanism to confirm priorities are being kept in clear view and they are not going off half baked.
Master Baker retrospective format
The team considers what they did not spend enough time on. What could have delivered greater value if only more time had been directed to it? What wasn’t delivered because there wasn’t enough time dedicated to it? These might be areas of sub-optimal performance or where the stories or tasks were under-estimated.
Here, the team lists which outputs delivered good value for the amount of time invested. What was delivered on time as predicted? These are deliverables and output where time estimations were on point and were also delivered at the right quality and timeframe.
Finally, the team reflects on where too much time was allocated or spent. Outputs may have been delivered, however they came at a considerable time and opportunity cost. Tasks were over-estimated or took too long to deliver. This represents learning opportunities to improve time estimations or time management.