Scrum Retros

If you're going to do Scrum, you gotta get retros right. They're what allow the process to evolve and enable the team to get better.

  1. Only the development team should be in the retro, it's for the team after all. Anyone else will make it less likely the team will speak up about anything. How can you say "Jen kept asking me to do things outside the sprint", when Jen is there?
  2. You have to revisit what was talked about in the previous retro. This is how you track that changes are actually happening and working.
  3. Good/Bad/Change or Start/Stop/Continue, both styles work. But Change & Start/Stop are the most important ones to follow up on.

Scrum should be a set of tools, not a ridge process.

Subscribe to WebDev news from

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.