ltig new projects_aug2010
DESCRIPTION
Start-up presentation for new (2010) Learning & Teaching Innovation Grant projects.TRANSCRIPT
Joint Information Systems Committee 09/04/23 | | Slide 1
Learning & Teaching Innovation Grants
Start-up Meeting: Welcome
Joint Information Systems Committee
Why Learning & Teaching Innovation Grants?
To help allow new and innovative ideas to filter through from the community that do not fit conveniently within a traditional JISC call for proposals
Lower administrative application process for institutions looking to bid
Particularly suitable for smaller projects
Joint Information Systems Committee 09/04/23 | slide 3
Activity Area knowledge base
Learning & Teaching Innovation Grants:Structure of programme
Round 1 (May 08)• 2 projects• Total: £150,000
At least £500,00 over the life of the programme (2008-2011) Open rolling call 5 rounds so far One year projects up to £50,000 (2010) and £75,000 (2008-9)
Round 2 (Aug 08)• 2 projects• Total: £110,413
Round 3 (Jan 09)• 5 projects• Total: £308,113
Round 4 (May 09)• 5 funded • Total: £260,519
Round 5 (Feb 10)• 5 funded • Total: £247,385
Joint Information Systems Committee
Reporting (i)
• Project plan• Consortium Agreement*• Interim report• Final report• Completion Report
Why?
• Public funds (audit requirement)• To appropriately promote
projects• To see how you are getting on• To offer appropriate support
Required reports
2 Aug 2010 1 Oct 2010 6 May 2011 30 Jun 2011
Project Plan & Budget
Consortium Agreement
(where applicable)
Draft Final Report
Final, Completion reports & Budget
30 Dec 2010
InterimReport & Budget
Very much encouraged: blogs / wiki / news feed (rss), etc.
09/04/23 | slide 4
Joint Information Systems Committee
• 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 aren’t 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.
09/04/23 | slide 5
Reporting (ii)
Joint Information Systems Committee 09/04/23 | slide 6
What works well in interim & final 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 didn’t work and how you addressed this
DON’T insert chunks of your project plan
just refer to work package numbers – name them!
make the reports “difficult” to read without prior knowledge
Joint Information Systems Committee 09/04/23 | slide 7
Templates & guidance
Templates & useful links available from the New Projects netvibes page
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
www.jiscinfonet.ac.uk
LTIG Projects Page
http://www.netvibes.com/hprice#new_eL_projects
http://www.jisc.ac.uk/whatwedo/programmes/elearningcapital/programmesupport/reportwritingworkshopDec08.aspx
Joint Information Systems Committee
Programme & project websites
- overview of project- project proposal - project plan (when available)- final reports (when available)- link to project website
- JISC branded & link back to programme- managed by project team- materials and reports- news and events (rss feed please)- project aims and objectives- methodology- planned outcomes- project partners- contact details
jisc.ac.uk
09/04/23 | slide 8
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.
project website
Joint Information Systems Committee
Any Questions?
09/04/23 | slide 9