An Agile retrospective is a meeting that's held at the end of an iteration. The process of retrospecting is at the heart of Scrum. During the retrospective review, the team reflects on what transpired during the iteration and identifies actions for improvement going forward.

The Agile retrospective can be thought of as a "Lessons Learned" meeting. The team reflects on how everything went and then decides what changes they want to make in the next iteration. The retrospective is accomplished by team collaboration, and team members should decide together how the meetings will be run and how decisions will be made about improvements.

During the retrospective, team members are asked the following questions:

	What worked well and we definitely want to do again?
	What did we learn from the iteration/sprint metrics?
	What did we learn that we want to do differently?
	Did we learn what the optimum story points are for an iteration?
	What did we learn in the flow of events?
	What can we do better in reporting project status?
	What did we NOT investigate or talk about that likely could stand improvement?

The Iteration Retrospective contains the following data elements:

	Date of the retrospective
	Project manager's name
	Who completed the retrospective?
	What questions will be asked in the retrospective meeting?
	What worked well?
	What can be improved?
	What do we want to try?
	What do we still not know?