Confirmed users
1,052
edits
No edit summary |
|||
| Line 1: | Line 1: | ||
==DRAFT Campaign Retrospective Agenda Template== | ==DRAFT Campaign Retrospective Agenda Template== | ||
We' | We're proposing doing 2 types of post-mortems (ahem, I mean retrospectives) for each Mozilla project: Release and Campaign. The release retrospective is to review schedule, scope, communication and more to improve on our processes. Campaign retrospectives will be conducted after a website or app is retired to review goals, metrics, ROI and the overall success of the product. | ||
The purpose is to learn from our mistakes as well as acknowledge and celebrate our successes. | The purpose is to learn from our mistakes as well as acknowledge and celebrate our successes. | ||
We should contain retrospectives to one hour. Here’s an agenda outline to help facilitate the meeting. Open communication is the goal. Finger pointing isn’t. When scheduling a retrospective, copy the below agenda into the meeting invite or send via email prior to the date. | |||
Title: | Title: | ||
| Line 14: | Line 14: | ||
Body: | Body: | ||
<nowiki> | <nowiki> | ||
You're invited to participate in a campaign retrospective for {Website Name}. Let's discuss | |||
the nitty gritty in a constructive way (no finger pointing!) and help make future projects run | |||
more smoothly. For each item below we will discuss “what went well,” “what can be improved” | |||
as well as the specific questions pertaining to each item. | |||
Intro | |||
* (Re)introduce the team | |||
* Provide general overview and recap of the project. | |||
Goals | Goals | ||
* List the goals for the site | * List the goals for the site | ||
* | * Were success metrics clearly defined? | ||
Metrics | |||
* Review the following: | |||
** Download conversions | |||
** Unique users | |||
** Page views | |||
** Other | |||
Analysis: | |||
* How did we do? | |||
Outcome/Summary | Outcome/Summary | ||
</nowiki> | </nowiki> | ||