IT/Production Acceptance/Retention

Start of project

Name each of the following:

• Project sponsor: D.Ronitzky
• Main IT contact: J.Fitzhugh
• Main WebDev contact: M.Morgan
• Main QA contact: S.Donner
• Main third party contact (if developed externally): AKQA (retention agency); James DeJesus (james.dejesus@akqa.com)
• Final application owner/maintainer: D.Rolnitzky

Overall goal of the project

• Improve Firefox Retention by creating a micro site where users can share a video with friends and family (fightagainstboredom.org). Users will find the micro site through email-to-a-friend, blog posts, facebook, and other outbound media. A Facebook app will be developed (by AKQA) that will allow users to add an "interingness" application to their FB page.
• VERY rough outline of the micro site and FB app page:

Facebook app: http://www.facebook.com/apps/application.php?id=6616108785 HTML page with working emailer: http://www.jamesdejesus.com/ffsite/

Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc):

• Goal is to have project up and running by week of 12/24/07
• Domain name "fightagainstboredom.org" purchased -- done
• Access to SVN needed -- done (see bug 403504)
• Staging server required -- done (see bug 408402)
• Urchin analytics needed on micro site -- in progress (bug 408932)
• Email relay information needed for send-to-a-friend functionality -- in progress (bug 408894)

Initial timeline

• Development week of 12/17/07

External dependencies

• AKQA development time, Mozilla creative signoff and approval, video production, facebook application development

Dev environment specs

• TBD

Staging Signoff

In order to get an app into staging, the following should be completed:

• Code committed to Mozilla source control and tagged: in process
• Initial architecture review by IT and WebDev: date complete?
• Site must be password protected: in process
• Review timeline to go live:
• Review any production requirements so IT can order any new hardware needed: none needed

Production Signoff/Launch

• Final WebDev signoff
• Final IT signoff
• Final QA signoff -- should use the following QA list as a guideline (http://wiki.mozilla.org/Firefox:Download_Page:Test_Plan)
• Operations documents filled for support & any training complete
• Monitors in place