Confirmed users
1,052
edits
Websites/Processes/Retrospectives/Website: Difference between revisions
Jump to navigation
Jump to search
Websites/Processes/Retrospectives/Website (view source)
Revision as of 18:10, 18 April 2011
, 18 April 2011no edit summary
Ryansnyder (talk | contribs) (Created page with "This is a placeholder for the meeting agenda and action items for retrospectives / post-mortems for a website or campaign.") |
No edit summary |
||
| Line 1: | Line 1: | ||
==DRAFT Campaign Retrospective Agenda Template== | |||
We'll be 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 site 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. | |||
We’ll try to contain retrospectives to one hour. Here’s an 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. | |||
Title: | |||
<nowiki> | |||
Campaign Retrospective Agenda for Mozilla Project XXX | |||
</nowiki> | |||
Body: | |||
<nowiki> | |||
To get a comprehensive review of all aspects of the project lifecycle, topics are broken down by phase and/or stakeholder. For each item below we will discuss “what went well,” “what can be improved” as well as the specific questions pertaining to each item. | |||
Goals | |||
* List the goals for the site | |||
* What were the success metrics? | |||
Metrics (how did we do?) | |||
* Download conversions | |||
* Unique users | |||
* Page views | |||
* Other | |||
Outcome/Summary | |||
</nowiki> | |||