Websites/Processes/Retrospectives/Release: Difference between revisions
Jump to navigation
Jump to search
Ryansnyder (talk | contribs) No edit summary |
|||
| Line 1: | Line 1: | ||
There are 2 types of retrospectives that we will perform for each Mozilla website - a release retrospective and a [[Websites/Processes/Retrospectives/Release|website / campaign retrospective]]. | |||
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. | |||
= Release Retrospective Agenda Template = | |||
We should 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: | Title: | ||
<nowiki> | <nowiki>Release Retrospective Agenda for Mozilla Project {Website Name} </nowiki> | ||
Retrospective Agenda for Mozilla Project {Website Name} | |||
Body: | Body: | ||
<nowiki> | <nowiki> | ||
You're invited to participate in a release retrospective for {Website Name}. Let's discuss the nitty gritty in a constructive | You're invited to participate in a release 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. | ||
way (no finger pointing!) and help make future projects run more smoothly. | |||
To get a comprehensive review of all aspects of the project lifecycle, topics are broken down by phase and/or stakeholder. | 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” and “what can be improved” as well as the specific questions pertaining to each item. | ||
For each item below we will discuss “what went well” and “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. | ||
Planning | Planning: | ||
* Were there clear requirements and a solid understanding of the website from the start? | * Were there clear requirements and a solid understanding of the website from the start? | ||
* Were goals and success metrics clearly defined? | * Were goals and success metrics clearly defined? | ||
Design | Design: | ||
* Were there sufficient user stories? | * Were there sufficient user stories? | ||
Resources | Resources: | ||
* Were roles / responsibilities clear? | * Were roles / responsibilities clear? | ||
* Were there sufficient resources to execute all phases smoothly within the project scope and schedule? | * Were there sufficient resources to execute all phases smoothly within the project scope and schedule? | ||
Schedule | Schedule: | ||
* Was the schedule realistic? | * Was the schedule realistic? | ||
* Did anything cause the schedule to slip? | * Did anything cause the schedule to slip? | ||
Development | Development: | ||
* Was code freeze respected? | * Was code freeze respected? | ||
QA testing | QA testing: | ||
* Did development adhere to QA’s checklist? | * Did development adhere to QA’s checklist? | ||
IT / Deployment | IT / Deployment: | ||
* Were there any issues getting the app onto stage? | * Were there any issues getting the app onto stage? | ||
* How did launch go? | * How did launch go? | ||
| Line 55: | Line 54: | ||
* Was string freeze respected? | * Was string freeze respected? | ||
Communication | Communication: | ||
* Were the channels of communication between all the stakeholders established from the start? | * Were the channels of communication between all the stakeholders established from the start? | ||
* Was there anything that blocked or hindered communication? | * Was there anything that blocked or hindered communication? | ||
Summary | Summary: | ||
Action items: | |||
</nowiki> | </nowiki> | ||
Revision as of 15:32, 24 April 2011
There are 2 types of retrospectives that we will perform for each Mozilla website - a release retrospective and a website / campaign retrospective.
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.
Release Retrospective Agenda Template
We should 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:
Release Retrospective Agenda for Mozilla Project {Website Name}
Body:
You're invited to participate in a release 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.
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” and “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.
Planning:
* Were there clear requirements and a solid understanding of the website from the start?
* Were goals and success metrics clearly defined?
Design:
* Were there sufficient user stories?
Resources:
* Were roles / responsibilities clear?
* Were there sufficient resources to execute all phases smoothly within the project scope and schedule?
Schedule:
* Was the schedule realistic?
* Did anything cause the schedule to slip?
Development:
* Was code freeze respected?
QA testing:
* Did development adhere to QA’s checklist?
IT / Deployment:
* Were there any issues getting the app onto stage?
* How did launch go?
Security
* Were there any issues in the security review process?
L10N
* Were there any issues in the localization process?
* Was string freeze respected?
Communication:
* Were the channels of communication between all the stakeholders established from the start?
* Was there anything that blocked or hindered communication?
Summary:
Action items: