| | 1 | = The Progressive Technology Project CRM review = |
| | 2 | |
| | 3 | The [http://progressivetech.org Progressive Technology Project] is working with approximately (??) X organizations who are interested in developing more effective database software for managing their organizing activities. Some of the groups include ... Some of their chief needs include ..... |
| | 4 | |
| | 5 | == Goals == |
| | 6 | |
| | 7 | The CRM review project will be a collaboration between May First/People Link and PTP with the following goals: |
| | 8 | |
| | 9 | * Better understand the database needs of grassroots organizing groups |
| | 10 | * Better understand the strengths and weaknesses of the existing free software vis-a-vis these particular needs |
| | 11 | * Provide direction for grassroots groups in evaluating their database options |
| | 12 | |
| | 13 | == Objectives == |
| | 14 | |
| | 15 | By the end of the project we would like to have: |
| | 16 | |
| | 17 | * Public documentation of our experiences, discussions and conclusions |
| | 18 | * Experience using demo versions of the software under consideration |
| | 19 | * A sense of which of the existing software packages would best meet the needs of the groups PTP is working with |
| | 20 | * A detailed proposal for changes that would need to be applied to the best candidate, how long it would take to implement those changes (and cost), and strategies for how to accomplish the work |
| | 21 | |
| | 22 | While Jamie (MFPL) will take the lead role and put in the main hours on the project, he will be working very closely with a defined PTP group that will provide timely feedback and direction. All discussion will happen in public forums (preferably as a ticket on https://support.mayfirst.org/). All documents will also be published via a wiki that can track changes (also, preferably on https://support.mayfirst.org/). |
| | 23 | |
| | 24 | == Proposed/Initial Timeline == |
| | 25 | |
| | 26 | * Week one |
| | 27 | * Create the team and come to agreement on goals of the project by modifying this proposal until everyone is in agreement with it. |
| | 28 | * Begin developing a needs document that outlines what features we are looking for |
| | 29 | * Agree on an initial short list of software packages to consider |
| | 30 | |
| | 31 | * Week two |
| | 32 | * Continue developing needs document |
| | 33 | * Begin demo installation of software package list. |
| | 34 | * Begin evaluating packages against list |
| | 35 | |
| | 36 | * Week three |
| | 37 | * Evaluate where we are. Are we coming close to finding a good package? Do we need to start over again? Or is it obvious that a package is the perfect candidate so no need to continue? |
| | 38 | * Depending on the outcome... continue package evaluation |
| | 39 | |
| | 40 | * Week four |
| | 41 | * Write up final evaluation and notes |
| | 42 | |
| | 43 | == Time/Compensation == |
| | 44 | |
| | 45 | Jamie would work approximately 10 hours/week on the project and would be compensated $3,000. |
