[SPIKE] Write a project retrospective for the Lagoon migration.

[ndouglas]

We should write a retrospective of the entire project and how we planned and executed it. It might be useful to Amazee.io, stakeholders, internal documentation for future initiatives, etc.

Tasks

• Collect project data and metrics – how long did this take, beginning to end? How long did specific phases take? What resources did it occupy? What issues were encountered? What decisions were made, and at what time?
• Identify successes and achievements - what did we do right? What was smooth?
• Analyze self-identified areas for improvement - What could’ve been done better? Where did communication or processes break down? Where did we have to switch gears or horses? What systemic things contributed to or caused these issues? What would we recommend? We should have a meeting about this where the principal team members discuss this.
• Gather feedback from outside team members and stakeholders - How did they feel about the process? Was it transparent? Responsible? Accountable? What deficits remain?
• Create action plan for followups - Ensure that every deficit in the retrospective report has a corresponding issue or AC somewhere to address and resolve it.
• Complete the retrospective report - Just write all this out in some coherent fashion.
• Distribute the retrospective report - To Amazee.io, stakeholders, ToT(?), put it in the repo, etc.

Acceptance Criteria

• A project retrospective has been completed by the team.
• The project retrospective has been socialized and/or distributed to interested parties.