Websites/Processes
The following processes are used to cover every aspect of a website's lifespan from beginning to end.
- Website roles and terminology
- Running meetings
- Sample projects and estimated time to deliver (forthcoming)
Ideation
The ideation phase is the process that includes brainstorming, prototyping, and creating product requirement documentation.
- Decider: Product Owner
- Driver: Product Owner
Process (Draft)
1. Product Owner emails the Web Project Manager to notify that individual of the web project.
2. Product Owner submits project to the Web Dev project manager.
3. Product Owner creates a wiki page for this site using either template:
4. Meet requirements for each group to begin Project Instantiation (forthcoming).
Kickoff
The kickoff phase is the process of forming a technical team and fleshing out details to begin the development phase.
- Decider: Product Owner
- Driver: Web Project Manager
Process
1. TPM and Web Project Manager execute tasks in checklists for project instantiation:
2. Web Project Manager schedules Kickoff Meeting.
Bringing New Developers on Board
If web developers are new to Mozilla projects, please use the following:
- Email boiler plate for New Contractors
- Email boiler plate for New Employees
- Getting started with Bugzilla
Implementation
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.
- Decider: Product Owner
- Driver: TPM
Mozilla Web Development Guidelines
During the implementation phase, the Web Dev and UX teams write the website code following Mozilla guidelines:
- Developers are expected to follow:
- At least 1 Mozilla web developer responsible for the code review of all code committed to the code repository.
- Bugzilla is the ticket tracking system that will be used to for bug reporting and project overviews. Developers are expected to adhere to the Bugzilla Workflow for tracking tickets.
Process
1. TPM schedules and drives the weekly meeting.
Once the initial code base has been created, and the website is functioning as indicated in the specs in a development environment, the remaining process may begin.
2. TPM ensures the stage server is up and running, and the website is functioning as indicated in the specs.
- Stage server will be set to auto-update from master branch of code repository every 5 minutes.
3. The following processes begin; each team follows Bug Life Cycle process.
- Accessibility Review begins.
- SEO Review begins.
4. Web Dev notifies TPM that all required strings and code have been committed to stage.
- Web Dev continues to fix bugs, but only commits code to a development branch.
5. TPM notifies team that:
- feature freeze is in effect.
- string freeze is in effect.
6. The following processes begin; each team follows Bug Life Cycle process.
- IT testing begins.
- Legal review begins.
- L10N process begins.
- QA testing begins.
7. QA signs off on initial round of tests.
8. TPM notifies team that code freeze is in effect.
- Web Dev continues to fix bugs, but does not commit code to master branch.
9. Infrasec testing begins; team follows Bug Life Cycle process.
10. TPM notifies team that code freeze is no longer in effect.
- Web Dev may again commit code to master branch.
11. QA signs off on final round of tests.
12. TPM prepares Bugzilla ticket for Production Push.
Deployment
The process of launching a new web product, or pushing changes to an existing web product, and communicating it to the community.
Process (Draft)
1. TPM drives deployment (please expand).
2. Post-launch, Web Project Manager schedules release retrospective meeting.
3. Web Project Manager documents and publishes retrospective results.
Supplementary Documents
End of Life
The end of life phase is the process of retiring a web product or website.
- Decider: Product Owner
- Driver: TPM
Process
1. Product Owner contacts Web Project Manager to begin retirement process, or Website Taskforce nominates and approves the retirement of a website.
2. Web Project Manager assigns a TPM to drive the retirement process.
3. TPM retires a page, a section of pages or the entire web site or product.
- Retire a Page or part of a Website
- Retire a Website
- Archive a Website
4. Web Project Manager schedules Website / Campaign Retrospective.
5. Web Project Manager documents results of retrospective.