IT/Production Acceptance/Sheriff Duty

< IT‎ | Production Acceptance
Revision as of 23:19, 17 June 2010 by Kourge (talk | contribs) (Created page with '== Start of project == * Name each of the following: ** Project sponsor ** Main IT contact ** Metrics contact ** Main WebDev contact ** Main QA contact ** Main Security contact *…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Start of project

  • Name each of the following:
    • Project sponsor
    • Main IT contact
    • Metrics contact
    • Main WebDev contact
    • Main QA contact
    • Main Security contact
    • Main third party contact (if developed externally)
    • Final application owner/maintainer
  • Outline the following:
    • Overall goal of the project
    • Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc)
    • Initial timeline
    • External dependencies
    • Dev environment specs
    • Does this project use any plugins or proprietary technology?

Staging Signoff

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

  • Code committed to Mozilla source control and tagged
  • Initial architecture review by IT and WebDev
  • Plugin/tech review by Evangelism
  • Security review must be in-process
  • Site must be password protected
  • Review timeline to go live
  • Review any production requirements so IT can order any new hardware needed

Production Signoff/Launch

  • Final WebDev signoff
  • Final IT signoff
  • Final QA signoff
  • Final Security signoff
  • Final Metrics signoff
  • Operations documents filled for support & any training complete
  • Monitors in place