JISC Information Environment Programme 20092011

1
JISC Information Environment Programme 2009-2011
Project Management

• This presentation
• Why is JISC funding you?
• Project reporting
• Websites
• Meetings events

2
why does JISC fund projects?

• Why JISC funds innovation programmes
• Enhanced capacity, knowledge and skills to enable
  positive and informed change in the sector
  (through piloting new technologies and
  approaches)
• Guidance to the sector on best practice models
  for using technology that can be used at
  departmental, institutional, regional or national
  levels.
• Strategic leadership to the sector and other
  bodies in specialist areas and to influence
  national and international agendas
• Knowledge and experience as a basis for future
  funding decisions for the JISC and its
  sub-committees
• New or enhanced services, infrastructure,
  standards or applications that may be used at
  departmental, institutional, regional or national
  levels
• http//www.jisc.ac.uk/fundingopportunities/project
  management/programmes.aspx

3
Why does JISC fund Repository Start-Up and
Enhancement Projects?

• Build Capacity (knowledge and skills)
• Increase number of repositories and volume of
  content available in them
• Increase quality of content in repositories
• Contribute to knowledge of good practice

4
reporting (i)

• Why?
• Public funds (audit requirement)
• To appropriately promote
• To see how you are getting on
• To offer appropriate support

Required reports

• Project plan
• Consortium Agreement
• Interim report
• Final report
• Completion Report

Very much encouraged blogs / wiki / news feed
(rss), etc.
5
reporting (ii)

• Budget reporting you should forecast whether
  you have over- or under- spent in each reporting
  period and agree any changes to your budget with
  your Programme Manager. Programme Managers would
  rather see you use resources effectively than be
  faced with a big budget variance at the end of
  the project.
• Staffing you should always report on any
  changes in staffing, or significant periods of
  absence.
• Issues and Achievements if things arent going
  to plan, say so, say why, and say how you are
  handling it. If you need help, say so, it is not
  failure, its just truthful reporting! Likewise
  where things are ahead of schedule, or working
  really well, say so, or your programme manager
  might not know about it.

http//www.flickr.com/photos/pchow98/396532989/
6
what works well in reports?

• real-life examples
• telling the story of your project/progress
• describing how any of your initial assumptions
  were/have been challenged
• sharing details of anything that didnt work and
  how you addressed this
• DONT
• insert chunks of your project plan
• just refer to work package numbers name them!
• make the reports difficult to read without
  prior knowledge

7
templates guidance

• Generic JISC templates guidance available from
  the main JISC website
• Useful guidance on final and completion report
  writing can be found in the Report Writing
  Workshop Resource Pack
• Further guidance can be found on the JISC
  Infonet website, covering
• Project management
• Risk management
• Contract negotiation
• Change management

http//www.jisc.ac.uk/proj_manguide.html
http//www.jisc.ac.uk/whatwedo/programmes/elearnin
gcapital/programmesupport/reportwritingworkshopDec
08.aspx
8
references

• Project management guidelines
• http//www.jisc.ac.uk/proj_manguide.html
• JISC Report Writing Workshop Resource Pack
• http//www.jisc.ac.uk/whatwedo/programmes/elearnin
  gcapital/programmesupport/reportwritingworkshopDec
  08.aspx
• JISC InfoNet InfoKits
• http//www.jiscinfonet.ac.uk/infokits/project-mana
  gement
• http//www.jiscinfonet.ac.uk/InfoKits/risk-managem
  ent
• http//www.jiscinfonet.ac.uk/InfoKits/contract-neg
  otiation
• http//www.jiscinfonet.ac.uk/infokits/change-manag
  ement

9
programme project websites
jisc.ac.uk

• - overview of project
• - project plan (when available)
• - final reports (when available)
• - link to project website
• - link to programme website, support info etc.

project website
- hosted by institution - materials and reports -
news and events (rss feed please) - project aims
and objectives - methodology - planned outcomes -
project partners - contact details - anything else
Remember All outputs and deliverables need to be
made available on or via your website which must
be maintained for at least 3 years following
project completion.
10
communicating and collaborating

• Talk to each other
• Identify specific areas to work on together
• Talk to RSP www.rsp.ac.uk
• Use mailing lists strand, prog, repositories,
  other

tag inf11
We encourage you to blog your attendance at
events, and to list them in your project
reporting. Note exchanges of ideas with other
projects its all useful to show how youve run
your project and worked within the community to
avoid reinvention and work smarter!
11
contact details

• Start-Up Strand
• Amber Thomas
• a.thomas_at_jisc.ac.uk
• twitter ambrouk
• skype amber_thomas
• Enhancement Strand
• Andy McGregor
• a.mcgregor_at_jisc.ac.uk
• Twitter andymcg
• Skype andrew.mcgregor77
• JISC-INF11-SUE_at_JISCMAIL.AC.UK
• JISC-INF11_at_JISCMAIL.AC.UK
• JISC-REPOSITORIES_at_JISCMAIL.AC.UK