At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Team retrospectives have a very long history in software engineering. Before agile development processes, these meetings usually happened at the end of a project. Agile practice puts this meeting as an essential element of each Sprint (aka iteration). Doing so helps the team improve its own process and facilitates self-organization.
For your study of this topic, use these resources.
This is a comprehensive course on Sprint Retrospectives. Everyone must watch these seven videos:
These videos provide additional explanation or instruction.
This activity will take about 30-60 minutes total.
(Clarify with your instructor the specific expectations) This must also be done before the start of the class session when your team will conduct its retrospective.
Your team members must come prepared having captured on their own the issues in preparation for the team activity. Clarify with your instructor the specific expectations.