Websites/Processes/Retrospectives/Website: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
==Campaign Retrospective Agenda Template==
There are 2 types of retrospectives that we will perform for each Mozilla website - a [[Websites/Processes/Retrospectives/Release|release retrospective]] and a website / campaign retrospective.


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 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.
= Campaign Retrospective Agenda Template =


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.
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.
Line 16: Line 18:
You're invited to participate in a campaign retrospective for {Website Name}. Now that the campaign is over, let's review goals, metrics, ROI and the overall success of the product. We'll discuss the nitty gritty in a constructive way (no finger pointing!) and help make future projects more engaging and successful. For each item below we will discuss “what went well,” “what can be improved” as well as the specific questions pertaining to each item.
You're invited to participate in a campaign retrospective for {Website Name}. Now that the campaign is over, let's review goals, metrics, ROI and the overall success of the product. We'll discuss the nitty gritty in a constructive way (no finger pointing!) and help make future projects more engaging and successful. 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
Intro:
* (Re)introduce the team
* (Re)introduce the team
* Provide general overview and recap of the project.
* 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?
* Were success metrics clearly defined?


Metrics  
Metrics:
* Review the following:
* Review the following:
** Download conversions
** Download conversions
Line 30: Line 32:
** Page views
** Page views
** Other
** Other
ROI:
* How much did we pay to develop this site?
* What was the cost per acquisition?


Analysis:
Analysis:
* How did we do?
* How did we do?
* What did we not measure, and how can we ensure we measure that in the future?


Outcome/Summary
Outcome / Summary:


  </nowiki>
  </nowiki>
1,241

edits

Navigation menu