canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,305
edits
Websites/Processes: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The following processes are used to cover every aspect of a website's lifespan from beginning to end. The process is a '''work in progress''' and will be updated and change over time based on what works best for Mozilla. The goal is to create a simple process that will allow a web project to run smooth and increase the likelihood of achieving the desired goals. | The following processes are used to cover every aspect of a website's lifespan from beginning to end. The process is a '''work in progress''' and will be updated and change over time based on what works best for Mozilla. The goal is to create a simple process that will allow a web project to run smooth and increase the likelihood of achieving the desired goals. | ||
Do you have any thoughts on this procss? Is something unclear or obviously wrong? Please contact [https://ldap.mozilla.org/phonebook/tree.php#search/malexis@mozilla.com Mike Alexis] with feedback as we need your help to improve the documentation and overall process. | Do you have any thoughts on this procss? Is something unclear or obviously wrong? Please contact [https://ldap.mozilla.org/phonebook/tree.php#search/malexis@mozilla.com|Mike Alexis] with feedback as we need your help to improve the documentation and overall process. | ||
= Project Logistics = | |||
* Website [[Websites/Processes/Terminology|roles and terminology]] | * Website [[Websites/Processes/Terminology|roles and terminology]] | ||
| Line 7: | Line 9: | ||
* Sample projects and estimated time to deliver (forthcoming) | * Sample projects and estimated time to deliver (forthcoming) | ||
= Ideation = | = Project Processes = | ||
== Ideation Phase == | |||
The ideation phase is the process that includes brainstorming, prototyping, and creating product requirement documentation. | The ideation phase is the process that includes brainstorming, prototyping, and creating product requirement documentation. | ||
| Line 14: | Line 18: | ||
* Driver: Product Owner | * Driver: Product Owner | ||
== Process | === Process === | ||
x. Product Owner emails the Web Project Manager to notify that individual of the web project. | x. Product Owner emails the Web Project Manager to notify that individual of the web project. | ||
| Line 60: | Line 64: | ||
x. Once all teams approve the PRD, the Kickoff phase may begin. | x. Once all teams approve the PRD, the Kickoff phase may begin. | ||
= Kickoff = | == Kickoff Phase == | ||
The kickoff phase is the process of forming a technical team and fleshing out details to begin the development phase. | The kickoff phase is the process of forming a technical team and fleshing out details to begin the development phase. | ||
| Line 67: | Line 71: | ||
* Driver: Web Project Manager | * Driver: Web Project Manager | ||
== Process | === Process === | ||
1. TPM and Web Project Manager execute tasks in checklists for project instantiation: | 1. TPM and Web Project Manager execute tasks in checklists for project instantiation: | ||
| Line 75: | Line 79: | ||
2. Web Project Manager schedules [[Websites/Processes/Meetings/Kickoff_Meeting_Agenda|Kickoff Meeting]]. | 2. Web Project Manager schedules [[Websites/Processes/Meetings/Kickoff_Meeting_Agenda|Kickoff Meeting]]. | ||
=== Bringing New Developers on Board === | ==== Bringing New Developers on Board ==== | ||
If web developers are new to Mozilla projects, please use the following: | If web developers are new to Mozilla projects, please use the following: | ||
| Line 82: | Line 86: | ||
* [http://blog.johnath.com/2010/02/04/bugzilla-for-humans/ Getting started with Bugzilla] | * [http://blog.johnath.com/2010/02/04/bugzilla-for-humans/ Getting started with Bugzilla] | ||
= Implementation = | == Implementation Phase == | ||
The implementation phase is the process of developing a new web product and getting approval from all teams who have been tasked to review the product. | The implementation phase is the process of developing a new web product and getting approval from all teams who have been tasked to review the product. | ||
| Line 89: | Line 93: | ||
* Driver: TPM | * Driver: TPM | ||
== Mozilla Web Development Guidelines == | === Mozilla Web Development Guidelines === | ||
During the implementation phase, the Web Dev and UX teams write the website code following Mozilla guidelines: | During the implementation phase, the Web Dev and UX teams write the website code following Mozilla guidelines: | ||
| Line 106: | Line 110: | ||
* [https://github.com/mozilla/playdoh Playdoh] will be used as the code base unless stated otherwise. | * [https://github.com/mozilla/playdoh Playdoh] will be used as the code base unless stated otherwise. | ||
== Process | === Process === | ||
1. TPM schedules and drives the [[Websites/Processes/Meetings/Weekly_Meeting_Agenda|weekly meeting]]. | 1. TPM schedules and drives the [[Websites/Processes/Meetings/Weekly_Meeting_Agenda|weekly meeting]]. | ||
| Line 146: | Line 150: | ||
12. TPM prepares Bugzilla ticket for Production Push. | 12. TPM prepares Bugzilla ticket for Production Push. | ||
= Deployment = | == Deployment Phase == | ||
The process of launching a new web product, or pushing changes to an existing web product, and communicating it to the community. | The process of launching a new web product, or pushing changes to an existing web product, and communicating it to the community. | ||
== Process | === Process === | ||
x. TPM drives deployment (please expand). | x. TPM drives deployment (please expand). | ||
| Line 162: | Line 166: | ||
x. Web Project Manager documents and publishes retrospective results. | x. Web Project Manager documents and publishes retrospective results. | ||
== Supplementary Documents == | === Supplementary Documents === | ||
* [[Webdev:Release-Checklist|Release Checklist]] | * [[Webdev:Release-Checklist|Release Checklist]] | ||
= End of Life = | == End of Life Phase == | ||
The end of life phase is the process of retiring a web product or website. | The end of life phase is the process of retiring a web product or website. | ||
| Line 173: | Line 177: | ||
* Driver: TPM | * Driver: TPM | ||
== Process == | === Process === | ||
1. Product Owner contacts Web Project Manager to begin retirement process, or Website Taskforce nominates and approves the retirement of a website. | 1. Product Owner contacts Web Project Manager to begin retirement process, or Website Taskforce nominates and approves the retirement of a website. | ||