6 Apr 2014

Scrum Retrospective & Preparation


A retrospective is a meeting held at the end of a sprint which has the main aim of improving the performance of the team during future sprints. It is probably the most important event from the teams point of view. 

There are usually a number of questions the team is asked,  such as:

What should we:

  1. Start doing.
  2. Stop doing
  3. Continue doing



  1. What did we do well, that if we don’t discuss we might forget?
  2. What did we learn?
  3. What should we do differently next time?
  4. What still puzzles us?



  1. What went well?
  2. What could be improved?

At the start of the retrospective the team is given some time to think about the questions and create comments.

If the team is in the same room for the retrospective they can write their comments on post-it notes and put them on a white board. If team is a blended on/offshore one then I don’t recommend sitting in a meeting room around a conference phone, either a virtual white board (e.g. en.linoit.com) or a wiki document can be used, with VOIP (e.g. Skype) for each team member. The comments are then discussed, prioritised and if actions are possible are assigned to the team or scrum master to progress.


Population of the comments can be done prior to the meeting. Each team member is directed to either populate a shared document or send their points to the scrum master who can add them. Then during the retrospective the document acts as list of items to discuss:


  • The time spent during the retrospective is reduced as there is no need for thinking time to create the items to discuss.
  • If working in a on/offshore blended team where a whiteboard can’t be used, then problems where everyone is trying to add their items to a shared document at the same time won’t occur.
  • It’s easier for the scrum master / project leads to pre-investigate any points which they are not aware of.
  • The items are pre-documented so less note taking is needed during the retrospective.


  • The activity is not seen as a priority over other work resulting in a lack of participation by some team members.
  • Once the retrospective has started team members feel they don’t need to add any more items.

Personally I prefer not to do pre-planning so that all team members get the time to think and contribute.

blog comments powered by Disqus

About Me

My first computer was a Commodore VIC-20, I had great fun trying to code text adventures and side scrolling shoot ‘em ups in BASIC. This helped me lead the way as the first in my school to pass a computer exam.

Currently I work as a Senior Software Engineer in Bedford for a FTSE 100 Company. Coding daily in C#, JavaScript and SQL. Outside of work I work on whatever is interesting me at that time.