Websites/Processes

The following processes are used to cover every aspect of a website's lifespan from beginning to end.

Overview

• Temp Notes - http://etherpad.mozilla.org:9000/webdev-processes
• Website roles and terminology.
• Running meetings.

Ideation

The ideation phase is the process that includes brainstorming, prototyping, and creating product requirement documentation.

• Decider: Product Owner
• Driver: Product Owner

Process (Draft)

• Submit your Project to the Web Dev project manager.
• Create a wiki page for this site based on the Website Template.
  • If this project is for an existing website, use the Existing Website Template.
• 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:

• New Website Process
• Existing Website Process

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

Process (Draft)

1. TPM schedules and drives the weekly meeting.

Supplementary Documents

• Code Best Practices Guidelines
• Code Review
• Bugzilla Workflow
• QA Process
• Security Guidelines
• Accessibility Review
• SEO Review

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

• Release Checklist

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. 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

2. Web Project Manager schedules Website / Campaign Retrospective.

3. Web Project Manager documents results of retrospective.