2014 Activity Plan/Development budget

Lead member of staff

Katherine Bavage

Indicative budget amount

£45,000

Description and overall rationale

The development budget seeks to support the day to day system administration of the Chapter’s IT infrastructure, including the hosting of its community and internal wikis, databases, email accounts and so on. This is vital to ensure as a movement entity we are managing data and donations in a secure and professional way. In addition, it seeks to solicit, develop and deliver community generated ideas for software projects that will support content production or improvement.

Timelines - i.e. what happens quarter by quarter

Success criteria and Metrics - overall and quarter by quarter breakdown if relevant

Goals

There are several key technical projects contributing to our strategic goals that WMUK is supporting in 2014, particularly VLE and QRpedia.

There are robust and efficient tools readily available to enable the creation, curation and dissemination of Open Content.

• 25% of VLE users go on to become active Wikipedians, making ten edits per month most months (VLE/Wikimetrics)

An increased diversity of Wikimedia contributors

• 25% of VLE users identify as female on registration or in user survey (VLE/Wikimetrics)

There are robust and efficient tools readily available to allow WMUK - and related organisations - to support our own programmes and to enable us to effectively record impact measures.

• QRPedia statistics are functional by 1 June and available to WMUK and other organisations

Additionally, we have a list of operational targets that capture the functioning of the WMUK IT infrastructure, and the support for UK technical community, these are explained below.

Support the day to day system administration of the chapter’s IT infrastructure

• Annual policy review and security audit, including certification of PCI compliance - Conducted by end of October 2014, with all amendment to policy/infrastructure passed by the board
• Updated training log for existing staff and new starters - Updated quarterly and all new starters to receive training within one month, whether online or in person (learning register)
• Regular progress meetings between staff/technical contractors - No less than every five weeks

Support community generated ideas for software projects to increase volunteer participation

• Number of community projects that are discussed at Technical committee and taken forward - Increase by 100% in 2014/15 (on wiki - meeting minutes)
• Regular meetings between staff/technical contractors/community members at Technology Committee - Minimum of six per year, at least two in-person (on wiki)
• Time to progress/close bugs registered through bugzilla that refer to community projects - Initial response within 5 working days (on bugzilla)
• Surveying community partners/wider community on responsiveness/effectiveness - over 50% ‘good’ or better on chapter’s ability to assist/support/deliver (survey)

Add operational consideration: The proportion of VLE users who describe the VLE as "effective" or "very effective" in the user survey - "At least 70% of respondents to the VLE user survey describe the tool as either effective or very effective"

Risks

No focus on what is to be achieved leads to underspend or wasted spend.