Websites/Processes/Retrospectives/Release - Revision history

Ryansnyder: /* Release Retrospective Agenda Template */

2011-04-24T15:37:26Z

Release Retrospective Agenda Template

← Older revision		Revision as of 15:37, 24 April 2011
Line 49:		Line 49:
	IT / Deployment:		IT / Deployment:
	* Were there any issues getting the app onto stage?		* Were there any issues getting the app onto stage?
			* Were there any issues getting the app onto production?
	* How did launch go?		* How did launch go?

Ryansnyder: /* Release Retrospective Agenda Template */

2011-04-24T15:36:00Z

Release Retrospective Agenda Template

← Older revision		Revision as of 15:36, 24 April 2011
Line 14:		Line 14:
	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 way (no finger pointing!) and help make future projects run more smoothly.		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.		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:		Intro:

Ryansnyder at 15:34, 24 April 2011

2011-04-24T15:34:17Z

← Older revision		Revision as of 15:34, 24 April 2011
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]].		There are 2 types of retrospectives that we will perform for each Mozilla website - a release retrospective and a [[Websites/Processes/Retrospectives/Website\|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 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.

Ryansnyder at 15:32, 24 April 2011

2011-04-24T15:32:13Z

← Older revision		Revision as of 15:32, 24 April 2011
Line 1:		Line 1:
	~~==DRAFT:~~ Release ~~Retrospective Agenda Template==~~		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]].

	~~We should be doing post-mortems (ahem, I mean retrospectives) for all Mozilla projects.~~ The ~~purpose~~ is to ~~learn from our mistakes~~ and improve our processes, ~~as well as acknowledge~~ and ~~celebrate our successes~~.		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.

	~~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.		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}
	</nowiki>

	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:

	~~Action items~~
	</nowiki>		</nowiki>

Jsocol: /* DRAFT: Release Retrospective Agenda Template */

2011-04-21T15:50:31Z

DRAFT: Release Retrospective Agenda Template

← Older revision		Revision as of 15:50, 21 April 2011
Line 12:		Line 12:
	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 way (no finger pointing!) and help make future projects run more smoothly.		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.		To get a comprehensive review of all aspects of the project lifecycle, topics are broken down by phase and/or stakeholder.
Line 27:		Line 28:

	Design		Design
	* ~~Did the product owner provide~~ sufficient user stories?		* Were there sufficient user stories?

	Resources		Resources
Line 41:		Line 42:

	QA testing		QA testing
	* Did ~~the~~ development ~~team~~ adhere to QA’s checklist?		* Did development adhere to QA’s checklist?

	IT / Deployment		IT / Deployment

Ryansnyder at 16:57, 15 April 2011

2011-04-15T16:57:46Z

← Older revision		Revision as of 16:57, 15 April 2011
Line 27:		Line 27:

	Design		Design
	* Did ~~creative~~ provide sufficient user stories?		* Did the product owner provide sufficient user stories?

	Resources		Resources
Line 36:		Line 36:
	* Was the schedule realistic?		* Was the schedule realistic?
	* Did anything cause the schedule to slip?		* Did anything cause the schedule to slip?

			Development
			* Was code freeze respected?

	QA testing		QA testing
	* Did the development team adhere to QA’s checklist?		* Did the development team 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 49:		Line 52:
	L10N		L10N
	* Were there any issues in the localization process?		* Were there any issues in the localization process?
			* Was string freeze respected?

	Communication		Communication

Ryansnyder at 16:48, 15 April 2011

2011-04-15T16:48:19Z

← Older revision		Revision as of 16:48, 15 April 2011
Line 7:		Line 7:
	Title:		Title:
	<nowiki>		<nowiki>
	Retrospective Agenda for Mozilla Project ~~XXX~~		Retrospective Agenda for Mozilla Project {Website Name}
	</nowiki>		</nowiki>

	Body:		Body:
	<nowiki>		<nowiki>
	You're invited to participate in a release retrospective for ~~the XXX project~~. Let's discuss the nitty gritty in a constructive way (no finger pointing!) and help make future projects run more smoothly.		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.		To get a comprehensive review of all aspects of the project lifecycle, topics are broken down by phase and/or stakeholder.
Line 23:		Line 23:

	Planning		Planning
	* ~~Was~~ there clear requirements and a solid understanding of the ~~app~~ 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?

Line 30:		Line 30:

	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?

Line 43:		Line 43:
	* 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?

			Security
			* Were there any issues in the security review process?

			L10N
			* Were there any issues in the localization process?

	Communication		Communication

Malexis at 00:14, 15 April 2011

2011-04-15T00:14:41Z

← Older revision		Revision as of 00:14, 15 April 2011
Line 12:		Line 12:
	Body:		Body:
	<nowiki>		<nowiki>
			You're invited to participate in a release retrospective for the XXX project. 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.		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		For each item below we will discuss “what went well” and “what can be improved” as well as the specific questions pertaining

Malexis at 00:08, 15 April 2011

2011-04-15T00:08:43Z

← Older revision		Revision as of 00:08, 15 April 2011
Line 5:		Line 5:
	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.		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>		<nowiki>
	~~Title:~~
	Retrospective Agenda for Mozilla Project XXX		Retrospective Agenda for Mozilla Project XXX
	</nowiki>		</nowiki>

Malexis: /* Mozilla Project Process Retrospective Agenda Template */

2011-04-15T00:07:23Z

Mozilla Project Process Retrospective Agenda Template

← Older revision		Revision as of 00:07, 15 April 2011
Line 1:		Line 1:
	==~~Mozilla Project Process~~ Retrospective Agenda Template==		==DRAFT: Release Retrospective Agenda Template==

	We should be doing post-mortems (ahem, I mean retrospectives) for all Mozilla projects. The purpose is to learn from our mistakes and improve our processes, as well as acknowledge and celebrate our successes.		We should be doing post-mortems (ahem, I mean retrospectives) for all Mozilla projects. The purpose is to learn from our mistakes and improve our processes, as well as acknowledge and celebrate our successes.
Line 10:		Line 10:
	</nowiki>		</nowiki>

			Body:
	<nowiki>		<nowiki>
	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,”~~ “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
Line 19:		Line 21:

	Planning		Planning
	* Was there clear requirements and understanding of the app from the start?		* Was there clear requirements and a solid understanding of the app from the start?
	* Were goals and success metrics clearly defined?		* Were goals and success metrics clearly defined?

	Design		Design
			* Did creative provide sufficient user stories?

	Resources		Resources
	* were roles/responsibilities clear?		* were roles/responsibilities clear?
	* Were there sufficient resources		* Were there sufficient resources to execute all phases smoothly within the project scope and schedule?

	Schedule		Schedule
Line 37:		Line 40:
	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?

	Communication		Communication
	* Were the channels of communication between all the stakeholders?		* Were the channels of communication between all the stakeholders established from the start?
			* Was there anything that blocked or hindered communication?

	Summary		Summary