Wikimedia Technology/Annual Plans/FY2019/TEC11: Support Fundraising Activities

This program describes in relatively general terms, the work that Fundraising Tech does to ensure that we are technically able to raise our annual budget. Many of the major strategic decisions about how and where we fundraise will not be captured here: Rather, those decisions and related outcomes come from Advancement. Fundraising Tech exists to support decisions coming out of Advancement, and ensure that their plans continue to be technically possible. It may be helpful to think of the Advancement department as Fundraising Tech's client.

Note: Historically, the total spend on Fundraising activities has been capped at 10% of the total operating budget. This encapsulates much of Advancement's budget, and all of the Fundraising Tech budget. Functionally speaking, any increases on either side must be coordinated such that we do not exceed our current cap.

Teams contributing to the program
Fundraising Tech

Annual Plan priorities
None. This is an Advancement support activity.

How does your program affect annual plan priority?
This is a fundraising activity and supports all other teams by enabling us to raise the target budget.

Program Goal
The Advancement teams are able to effectively use required fundraising tools, and run all planned fundraising campaigns without technical blockers. Donor-facing and internal fundraising features are maintained or improved.

Donor privacy and security are maintained or improved.
 * Outcome 1
 * Campaign support and any regressions within the fundraising infrastructure are addressed in a timely manner, to minimize or eliminate negative technological impact on all fundraising campaign targets.
 * Output 1.1
 * In Q1, 3 and 4: Fundraising campaigns are supported but are subject to change and managed within standard work weeks.
 * Output 1.2
 * In Q2: Maximize fundraising infrastructure uptime, and promptly address scalability issues that only surface in high-traffic conditions.


 * Outcome 2
 * Donor privacy and security are maintained or improved.
 * Output 2.1
 * We stay current on security alerts and updates, and perform regular maintenance on the fundraising infrastructure.
 * Output 2.2
 * Maintain current security procedures and compliance standards for fr-tech and advancement teams


 * Outcome 3
 * Develop new features  and improve internal systems to support growing fundraising activities and reach. Investigate or enhance donor retention.
 * Output 3.1
 * Re-architect Contribution Tracking system to improve internal visibility, reliability and scale.
 * Output 3.2
 * Improve the CiviCRM dedupe functionality and balance that with other CRM requests.
 * Output 3.3
 * Keep up to date on current payment systems integrations, or integrate with new providers to maintain reach and flexibility.

Outcome 1

 * Campaign support and any regressions in current fundraising infrastructure are addressed in a timely manner.


 * Target
 * Advancement campaigns and Major Gifts are supported or are adjusted in coordination with the appropriate team.


 * Measurement method
 * 1) Regular work hours are observed. Bugs and campaigns adjusted to respect this.
 * 2) New non-critical tasks triaged within 7 calendar days.

Outcome 2

 * Donor Privacy and security are maintained or improved.


 * Target 2
 * Code freeze on Payment and CentralNotice systems is maintained. Unbreak Now issues are resolved as soon as possible.


 * Measurement method
 * 1) Code Freeze rules are reviewed and maintained.
 * 2) All New tasks triaged every business day. All Unbreak Now tasks addressed as soon as possible.

Outcome 3

 * Develop new features  and improve internal systems to support growing fundraising activities and reach. Investigate or enhance donor retention.


 * Target 3
 * Email and Banner campaigns are more reliable and can continue when fundraising infrastructure maintenance occurs. Changes to the contribution tracking Table allow the primary DB server to be taken down while accepting donations


 * Measurement method
 * 1) Conduct 1 live successful test: taking down the primary DB server while a campaign is live.
 * Target 4
 * Advancement will have more trust in the accuracy of CiviCRM records. The automatic CRM dedupe function identifies and merges more duplicate contacts per pass. Other CRM improvement requests are prioritized as needed.


 * Measurement method
 * 1) The automatic dedupe function handles 20 more types of conflicts.
 * 2) We ship more than just dedupe improvements to CiviCRM.
 * Target 5
 * The Advancement team can keep up to date on changing payment provider systems.


 * Measurement method
 * 1) Address emergencies and outages from payment providers.
 * 2) Fr-tech can demonstrate evaluation, estimation and possibly implement new opportunities in coordination with Advancement.

Dependencies
Fr-tech relies on Advancement for feedback, testing and general coordination of fundraising activities.