Projects that use Agile with Scrum use sprints to promise features to their product owner (customer/manager); sprints usually take place over a 30 day period. At the end of a sprint, teams conduct sprint retrospectives. These meetings discuss what was delivered from the team during the sprint, what processes were effective or ineffective (or could be improved upon), as well as actions to take place during the next sprint. In essence, they are small postmortems during development.
This section is simply a list of features the team completed during the sprint that the product owner receives. It is important to note that these are not tasks, but features. In Agile with Scrum, the features are found in the Product Backlog (List of the game’s features).
What Processes Were Effective:
This section lists the processes team members found effective during the sprint and would like to see in future sprints. Additionally, a vote is taken to see how many members of the team feel that way about that process.
What Processes Had Negative Effects (Or could be improved):
This section allows members to voice what processes they felt impeded progress due to inefficiencies, or need improvement to be made effective. Team members vote to see how many people in the team feel the same way.
Sprint retrospectives provide a way for team members to reflect on the past sprint and analyze what they liked and disliked during the sprint. I have seen many great things come out of these meetings and future sprints have truly improved based on members voicing their concerns to the team. I believe sprint retrospectives should be applied to all game developments. Even if the team isn’t using Agile with Scrum, a postmortem at every milestone still provides useful insight.