Changes between Version 20 and Version 21 of projects/crm_review/report

Oct 23, 2008, 1:49:28 PM (12 years ago)
Jamie McClelland



  • projects/crm_review/report

    v20 v21  
    2121 * '''Themes:''' We will develop a custom Drupal theme for the project designed to meet our own design/layout needs.
     23 * '''Tutorials and training materials:''' CiviCRM [ documentation] is fairly extensive, including loads of [ tutorials]. We'll probably want to sift through what's out there and come up with a re-usable set of training materials appropriate for our audience.
    2325== Customizations ==
    3537The project should provide a public facing web site, explaining the goals and providing links to download the components so that anyone can use it. Ideally, the configuration files and code generated should be kept in a revision control system and an issue tracker should be setup to track problems and provide for an easy method to fix problems and release new versions that can be tracked against new versions of CiviCRM.
     39== Timeline and Costs ==
     41Only developer hours are shown, not PTP hours.
     43=== Shared components and Hosting ===
     45 1. 1 - 2 hours: Initial project infrastructure setup (simple public web site, code repository, email list, etc.).
     46 1. 1 - 2 hours: virtual server setup that will be used for shared hosting (plus non-labor cost: $300/month)
     47 1. Demo setup. The developer in close partnership with PTP will setup a demo version of our configuration that will remain up throughout the project. We will create version one of our components by creating the demo site.
     48  * 1 hour: Install demo Drupal/CiviCRM site.
     49  * 2 - 4 hours: Setting up common configuration on demo site (and keep human-readable notes). This work includes all the point and click web-based configuration. Most of this work will be done by PTP. 
     50  * 5 - 10 hours: template customizations and language file changes. Once we've setup the local template directory and developed a system for the language changes, it should be relatively easy to make these changes. The more time consuming part will be deciding exactly which changes to make.
     51  * 5 - 10 hours: Custom dashboard display Drupal Module. A custom initial landing page will be created that will provide very specific statistics on how the database is being used by organizers, and will include an option to have reports emailed on a regular basis.
     52  * ? - ? hours: Additional custom reporting modules?
     53  * 5 - 10 hours: Custom drupal theme development. I'm not sure how much we want to invest in the custom theme - I think keeping it as simple as possible is the best idea since we would want to encourage people to use the same Drupal installation for the main web site - meaning they would want their own custom theme.
     54 1. 5 - 10 hours: Abstraction of demo project into generic, releasable files.
     55 1. 5 - 10 hours: Development of training materials
     57=== Customizations ===
     59Below are estimates for a single group. Mileage will vary tremendously based on each group.
     61 1. 2 hours: initial consultation
     62 1. 2 - 4 hours: Gaining familiarity with the setup, develop transition plan
     63 1. 1 hour: Setup, installation the components and setting up the initial database
     64 1. 0 - 25 hours: importing data from existing data sources. Some organizations may have nothing to import, some may have simple contact lists (name, phone number, address, etc.). Those will be relatively easy given CiviCRM's import features. Others may want to import existing membership data, donation data or other related data that could get really really hairy.
     65 1. Initial support and training
     66  * 2 hours: Initial 1 hour training for advanced staff
     67  * 2 hours: 1 hour training for all staff
     68  * 2 hour: follow up training/trouble shooting
     69  * 5 - 10 hours: phone support 1 - 2 months following adoption
     70 1. Ongoing support and training: depending on group - could be 0 - 5 hours/month