I like to schedule an 'as needed' Release retrospective with my teams for them to inspect the release from a holistic, big picture point of view. It's essential to pause from the nitty gritty of everyday coding/testing so they can review the release process and course correct/pivot if necessary.
The list below includes some questions that I ask the team to mull over, so they can pinpoint, assess and identify improvements.
Questions to consider:
To save the team time and to allow for some serious juicy conversation, I will forward this list of considerations a few days ahead of time.
Just an agile-dork writing about dorky agile things.