Processes/systems/ways of working can always be improved. Retrospectives are a tool that helps teams identify areas where they succeeded and where they could have done better. Team members can use the retrospective to identify steps that need to be taken to improve future projects.

In his book, Surviving Object-Oriented Projects, Alistair Cockburn described how working incrementally and regrouping after each increment could help project development.In 2001, Cockburn further developed his concept and even gave the first name to this famous-to-come team meeting, 'reflection workshop.' In the process, he contributes to the Agile Manifesto's birth (of which he is a co-signatory).

A successful retrospective reviews what happened and also deals with the present and the future of the team.
Start Stop Continue is a well-known action-oriented retrospective technique. It is designed to let people share practical ideas to improve as a team.
This simple yet powerful retrospective framework leads your team to think about three core questions:

• What should we start doing? (adjustments the team would be willing to implement in the next cycle)
• What should we stop doing? (things that don't help the team / don't show results)
• What should we continue doing? (activities that are working well, delivering results, and being positively perceived by the team)

Schedule 30-60 minutes to conduct a retrospective. If in person, have each person write down at least one start, one stop and one continue and place them into respective columns to review. If running this remotely, create a shared document with an analogous format.

Templates here and here.

https://www.goodreads.com/en/book/show/981742 https://resources.scrumalliance.org/Article/key-values-principles-agile-manifesto