Iteration Retros – The Airing of Grievances

One of the better teampractices in software development is to hold retrospectives after every development cycle(iteration, sprint, release, etc.). Iteration retros give the team an opportunity to review the user-stories (requirements) that werecompleted and discuss ways of improving the next development cycle so the same mistakes aren’t repeated.

The usual format is to review the iteration and then have the team discuss what went right, what went wrong, and what we could do better. When itera...