IT/Production Acceptance/CRM
From MozillaWiki
< IT | Production Acceptance
Contents
Start of project
- Name each of the following:
- Project sponsor -- Jay Patel
- Main IT contact -- Oremj?
- Main WebDev contact -- Morgamic?
- Main QA contact -- Stephen Donner
- Main third party contact - Chicago Technology Cooperative (CTC)
- Developer - Tom Wolf (tom at chicagotech dot org)
- Managing Parter - Jim Craner (jim at chicatotech dot org)
- Final application owner/maintainer -- Jay Patel / Mozilla Marketing / MoFo
- Outline the following:
- Overall goal of the project -- Mozilla would like to understand who is in our community. This project is would be a way for Mozilla to learn who is working on what inside Mozilla. The CRM would also be used for new community members to "sign up" for information at various conferences to become more involved. Mostly, it will be used by the community to update each other on what they are doing, how they can interact, where they are living or traveling (so people can meet up), and what they may need or what they have received as support from Mozilla.
- Any pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc)
- Technology: Drupal 6 + CiviCRM 2
- Server: We will need a dedicated server that can host a fairly robust CRM application that will likely contain thousands (or even tens of thousands) of records
- Standard server config for Drupal/CiviCRM + mail server access
- Staffing: One IT admin (Oremj?) and two application owner/maintainers (likely Jay Patel and Alix Franquet for the short-term)
- Monitoring: General server monitoring for uptime and database backups
- Response time: N/A
- Initial timeline
- Phase 1: Drupal/CiviCRM configuration and prototype development (December 2008)
- Demo of MozillaCRM (January 2009)
- Phase 2: Advanced features and theme development (Q1 2009)
- Phase 3: Polish and bug fixing (Q2 2009)
- Launch: Community beta release (Q2 2009)
- External dependencies
- Contract with CTC (Legal reviewing/negotiating as of 11/19)
- CTC development and updates to SVN (Ongoing through Q2 2009)
- Dev environment specs
- SVN access for CTC developers
Milestones and Tasks needed to get to completion
- Milesonte 1: Secure development firm for MozillaCRM (Completed)
- Finished RFP and initial legal review; contract pending with CTC
- Milestone 2: Setup Drupal/CiviCRM and check into SVN (Week of 11/25 or 12/1)
- IT sets up server and provides SVN access to CTC developers
- Milestone 2: Phase 1: Prototype development completed (12/31)
- Basic admin interface and user profile functionality implemented
- Security and legal requirements are met
- Milestone 3: Community user import and invitations (Jan 2009)
- Mozilla Campus Reps and l10n communities are imported
- Invitations go out to community members to populate the CRM
- Milestone 4: Demo MozillaCRM to Mozilla Marketing
- Milestone 5: Phase 2 (Q1 2009)
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
- 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
- Operations documents filled for support & any training complete
- Monitors in place
