2014 Activity Plan/Development budget: Difference between revisions
Jump to navigation
Jump to search
m (note) |
(goals) |
||
| Line 6: | Line 6: | ||
;Description and overall rationale | ;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 | ;Timelines - i.e. what happens quarter by quarter | ||
| Line 14: | Line 14: | ||
<div class="NavFrame collapsed"> | <div class="NavFrame collapsed"> | ||
<div class="NavHead">Goals</div> | <div class="NavHead">Goals</div> | ||
<div class="NavContent"> | <div class="NavContent" style="text-align:left"> | ||
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) | |||
**VLE supported for funding - lead in developing the project from the Education Committee | |||
*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) | |||
</div> | </div> | ||
</div> | </div> | ||
;Risks | ;Risks | ||
Revision as of 10:42, 18 December 2013
- 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
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)
- VLE supported for funding - lead in developing the project from the Education Committee
- 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)
- Risks