Dashboard > CRM > ... > Kabissa - CiviCRM Project Specifications > Kabissa - CiviCRM Statement of Work
Kabissa - CiviCRM Statement of Work Log In | Sign Up   View a printable version of the current page.

Added by Donald A. Lobo , last edited by Donald A. Lobo on Jun 26, 2007  (view change)
Labels: 
(None)

CiviCRM will implement the Kabissa requirements as specified on the wiki at Kabissa - CiviCRM Project Specifications. CiviCRM will implement the project in two phases. Each phase is expected to take approximately 100 hours (i.e. a total of 200 hours). The first phase will implement Spec 1 and 2. The next phase will implement specs 10 and 3. CiviCRM will have a working sandbox of the current state so Kabissa can validate and provide feedback at: Kabissa Sandbox. CiviCRM will comment on the specs if needed, we will also be maintaining tech notes at Kabissa - CiviCRM Tech Notes.

Project Guidelines

  • Reuse core CiviCRM functionality in as many places as possible. This will result in a modification of the specs on the wiki and CiviCRM will advise Kabissa about this and the potential options.
  • Kabissa is responsible for theming, deployment and system administration/operations. All CiviCRM / Drupal code will be stored in subversion (http://svn.civicrm.org/trunk and http://svn.quest.civicrm.org/kabissa/trunk). At the time of deployment, we will branch the repositories and tag them appropriately in coordination with Kabissa.
  • All issues / bugs and feature requests will be filed on the CiviCRM issue tracker at http://issues.civicrm.org/
  • CiviCRM will maintain the number of hours they worked on the project at Kabissa - Time Tracking. This page will be updated on a weekly basis during the development cycle.
  • Areas outside CiviCRM's expertise (Drupal Taxonomy) will take more time as CiviCRM engineers get up to speed on them. For such areas CiviCRM will notify Kabissa about it before starting work.

Project Schedule

Phase 1

June 18 - June 22 Project Scope, Statement of Work, Detailed spec review 10 hours
June 25 - June 29 Implement Spec 1 45 hours
July 2 - July 6 Implement Spec 2 50 hours

Detailed Phase 1 estimates (spec 1)

  • Schema Design and implementation: 5 hours
  • Form and Wizard Structure: 5 hours
  • rules and database code: 5 hours
  • unique profile url locker code: 5 hours
  • review application process: 10 hours
  • enhance civicrm search (add kabissa component) to enable above process: 5 hours
  • custom kabissa search screen for review application: 5 hours
  • misc: 5 hours
  • total: 45 hours

Detailed Phase 1 estimates (spec 2)

  • Kabissa locker page design and implementaion: 10 hours
  • View application: 10 hours
  • Enhancements to form to incorporate edit features and pages: 10 hours
  • Backend ping process: 15 hours
  • misc: 5 hours
  • total: 50 hours

Phase 2

TDB

Powered by a free Atlassian Confluence Open Source Project License granted to CiviCRM . Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators