Websites/Processes/Existing Website: Difference between revisions
Jump to navigation
Jump to search
Ryansnyder (talk | contribs) (Created page with "This lists all of the tasks necessary to get a project for an existing website started. After receiving a project from a Product Owner and agreeing to move forward, the Projec...") |
No edit summary |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Webdev/Processes|Existing Website]] | |||
This lists all of the tasks necessary to get a project for an existing website started. | This lists all of the tasks necessary to get a project for an existing website started. | ||
| Line 9: | Line 10: | ||
Verify that the following tasks have already been performed for this website: | Verify that the following tasks have already been performed for this website: | ||
* Verify that a wiki page has already been created for this website. If not, create using the [[Websites/Processes/Website_Template|Website Wiki Template]]. | * Verify that a wiki page has already been created for this website. If not, create one using the [[Websites/Processes/Website_Template|Website Wiki Template]]. | ||
* Verify that the Bugzilla component for this website already exists. | * Verify that the Bugzilla component for this website already exists. | ||
* Verify the site info has been added to the [[ | * Verify the site info has been added to the [[Websites/Active_List|Active Websites List]] page. | ||
* If a password is required for stage access, verify that it is documented in the [https://intranet.mozilla.org/Websites/Stage_Passwords Stage Credentials] page. | * If a password is required for stage access, verify that it is documented in the [https://intranet.mozilla.org/Websites/Stage_Passwords Stage Credentials] page. | ||
* Ensure that the developers assigned to this project have read / write access to the code repository. | * Ensure that the developers assigned to this project have read / write access to the code repository. | ||
| Line 18: | Line 19: | ||
* Define primary and secondary individuals for [[Websites/Processes/Terminology#Roles|project roles]]. | * Define primary and secondary individuals for [[Websites/Processes/Terminology#Roles|project roles]]. | ||
* Create the [[Websites/Processes/New_Website#Bugzilla_Tickets|Bugzilla Tickets]] for this project. | * Create the [[Websites/Processes/New_Website#Bugzilla_Tickets|Bugzilla Tickets]] for this project. | ||
* | * Email John Slater and CC Mike Alexis to get Creative involved early. They will provide Copy and Design. | ||
* Schedule the [[Websites/Processes/ | * Schedule the [[Websites/Processes/New_Website#Weekly_Meeting|Weekly Meeting]], if necessary. | ||
== Bugzilla Tickets == | == Bugzilla Tickets == | ||
Latest revision as of 22:11, 22 September 2011
This lists all of the tasks necessary to get a project for an existing website started.
After receiving a project from a Product Owner and agreeing to move forward, the Project Manager will execute all of the tasks on this list.
Existing Website Iteration Process
Verification Checklist
Verify that the following tasks have already been performed for this website:
- Verify that a wiki page has already been created for this website. If not, create one using the Website Wiki Template.
- Verify that the Bugzilla component for this website already exists.
- Verify the site info has been added to the Active Websites List page.
- If a password is required for stage access, verify that it is documented in the Stage Credentials page.
- Ensure that the developers assigned to this project have read / write access to the code repository.
Process
- Define primary and secondary individuals for project roles.
- Create the Bugzilla Tickets for this project.
- Email John Slater and CC Mike Alexis to get Creative involved early. They will provide Copy and Design.
- Schedule the Weekly Meeting, if necessary.
Bugzilla Tickets
Create the following bugs for a new website project:
- Create the Webtrends Ticket to track new implementations.
- Create the Security Ticket, if needed.
- Create the Privacy and Legal Ticket, if needed.
- Create the Production Release Ticket.