From Fedora Project Wiki

m (Created page with 'At the end of every release cycle, the Marketing team looks back on what it's accomplished during the release, in order to see how things can be improved for the next one. Th...')
 
No edit summary
Line 1: Line 1:
At the end of every release cycle, the [[Marketing]] 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 "postmortem," and it's a nice pause between the hecticness of release cycles (and traditionally serves as a point of leadership transition for the team, when applicable).
At the end of every release cycle, the [[Marketing]] 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," and it's a nice pause between the hecticness of release cycles (and traditionally serves as a point of leadership transition for the team, when applicable).


For instructions on how to run a Marketing postmortem, see the [[Marketing postmortem SOP]].
For instructions on how to run a Marketing postmortem, see the [[Marketing retrospective SOP]].

Revision as of 21:14, 6 July 2010

At the end of every release cycle, the Marketing 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," and it's a nice pause between the hecticness of release cycles (and traditionally serves as a point of leadership transition for the team, when applicable).

For instructions on how to run a Marketing postmortem, see the Marketing retrospective SOP.

This category currently contains no pages or media.