The agile method of holding retrospectives after every iteration offers the chance for immediate improvements while the project is still in motion, benefiting the current project. (This is different from a traditional project, where retrospectives,
or lessons learned, are usually held at the end of a project. These retrospectives offer lessons learned to the next project manager, who may or may not read the information). The other responses are incorrect. Retrospectives are not
an opportunity to remove project team members; retrospectives do not exist to prove to stakeholders the project team’s role; the team leader will already know the status of the iteration.