Projects Changes

Summary of proposed changes to the projects mechanism as they were discussed at the Development Meeting on 7th May 2014. For full details see linked document at end.

Development Meeting

• cull admin stuff
• focused activity reports - selected in advance maybe up to 4 per meeting
• lightweight non prescribed nature
• twice monthly
• change location e.g. 1.15
• attendance encouraged, particularly CSOs
• could include sign-off discussions

Project Submission

• no more tri-annual project round
• project submission form "alongside" support form
• any user can submit at any time (including us)
• will be public list of submitted projects
• like/dislike buttons

Prioritisation

• based on "informatics annual computing plan"
• mandatory - told to do it e.g. HoS , HoC , legislative, internal security etc
• strategic goals - meets a numbered goal mentioned in the plan
• objective (non-goal) - in strategy for year ahead but not a numbered goal
• annual plan can change during the year
• includes our own projects

Review

• submitted projects go to random unit head
• chooses a target priority - one of mandatory, strategic or objective
  • plus justification
• sets a deadline
  • plus justification
• two way process (possibly consultation beyond unit head)
• big projects would get broken down - upper limit ~4wks
• ideally respond within a week with yes/no
• project may just be evaluation

Admin

• CEG has new weekly project slot to deal with project admin
• prioritise and assign projects
• monitor progress of current projects

Effort

• projects will have a monitoring frequency set
• effort returned at that frequency
• unit heads to commit overall and per-project effort for their unit up front e.g. month ahead

Promotion/Engagement

• live lists of active projects (effort being spent on them)
• per-project blogs
• sign-off school wide invited talks + itpf
• external publication e.g. sourceforge

-- TimColles - 07 May 2014

• projects_review_final.pdf: projects_review_final.pdf