From Fedora Project Wiki

At the end of every release cycle, the CommOps team looks back on what it's accomplished during the release in order to see how things can be improved for the next one. This process of reflection is called a "retrospective". It's a nice pause between the craziness of release cycles to reflect on what and how things went (and traditionally serves as a point of leadership transition for the team, when applicable).

For instructions on how to run a CommOps retrospective, see the Marketing retrospective SOP as an example template.

Pages in category "CommOps retrospective"

The following 2 pages are in this category, out of 2 total.