• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
What Jisc Wants 10.12.08
 

What Jisc Wants 10.12.08

on

  • 566 views

 

Statistics

Views

Total Views
566
Views on SlideShare
566
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    What Jisc Wants 10.12.08 What Jisc Wants 10.12.08 Presentation Transcript

    • What does JISC want? Paul Bailey
      • Realising the benefits
      • eLearning Programme Outcomes & Benefits
      • eLearning Evaluation Framework
      David Kernohan, JISC
      • The programme manager view
      • Example final report
      • What programme managers want (and don’t want) in a final report
      Heather Williamson, JISC
      • JISC templates & general guidance
      • Templates & Guidance
      • Final Report (inc draft report)
      • Completion Report
    • JISC templates & guidance
      • generic JISC templates & guidance is available from the main JISC website
      • specific guidance for eLearning projects will be found on the Report Writing Workshop page
      • expected that this may be updated to reflect your feedback from today
      • you will receive an email when this is available
      http://www.jisc.ac.uk/proj_manguide.html http://www.jisc.ac.uk/whatwedo/programmes/elearningcapital/programmesupport/reportwritingworkshopDec08.aspx
    • A tale of two reports
      • The end of your project requires two reports to be submitted to JISC
        • The Final Report
        • The Completion Report
      • These reports have different audiences and will need to be written accordingly
      http://www.flickr.com/photos/machado17/139365709/
    • the final report
      • Audience:
      • HE/FE institutions, the wider community and JISC
      • Consider :
      • Your audience.
        • What will interest them?
        • Do not assume technical knowledge, or knowledge of your institution or of the acronyms that you use
      • How your project contributes to the programme/strand it is funded under.
      • Your evidence – your report needs to include information on (or point to) all of your project deliverables.
      • Merging or adding extra headings/sections to your final report if this will help the flow.
      • The length or your report.
      • Navigation. Make it easy to navigate.
      • Draft version required (usually at least a month before the final version is due)
      • Format:
        • Exec Summary
        • Background
        • Aims & Objectives
        • Methodology
        • Implementation
        • Outputs & Results
        • Outcomes & Impact
        • Conclusions & Recommendations
        • Implications for the future
      http://www.flickr.com/photos/e06158/2956432732/
    • deliverables, outcomes & impact
      • Deliverables:
        • Reports
        • Products
        • Services
      • Outcomes: changes resulting from the project, in:
        • behaviour
        • knowledge
        • skills
      • Impact:
        • Fundamental change in organisation/the wider community in the longer term [How does this manifest itself?]
      http://www.flickr.com/photos/karoluslinus/2487021800/ Remember: All outputs and deliverables need to be made available on your website which must be maintained for at least 3 years following project completion.
    • a little bit about the draft final report
      • This is used to give you some steer and feedback before you submit your completed version
      • Usually needs to be sent to your programme at least one month before your Final Report is due (often earlier than this)
      • Needs to provide your programme manager with a good idea of the scope, layout and content of your report
      • The draft does not need to be detailed - headings with bullet points beneath would be acceptable, but you can use more detail if you like
      http://www.flickr.com/photos/youngandwithit/3083062189/
    • the completion report
      • Audience:
      • JISC
      • Overview:
      • private between you and JISC
      • not intended to be onerous
      • brevity is encouraged
      • not all questions will be relevant to all projects
      • answers to questions may be used in evaluating whether the programme has produced benefits to the community but all identifying information will be removed
      • a draft version is not usually required (do check with your programme manager)
      £
    • contact details
      • Your programme manager is your first point of contact for any queries you may have:
      • Paul Bailey p.bailey@jisc.ac.uk (Sarah Davies)
      • Myles Danson [email_address]
      • Lisa Gray [email_address]
      • David Kernohan [email_address]
      • Sarah Knight [email_address]
      • Laura Pachkowski [email_address]
      • Heather Williamson [email_address]
    • “ Project Truthiness” Cartoon not available due to copyright reasons, use link below to view http://www.flickr.com/photos/pchow98/396532989/
    • 8 out of 10 Programme Managers who expressed a preference said that their cats preferred it… Infohttp://www.flickr.com/photos/opendemocracy/575778823/
    • the ASSPOO project final report Please note - this is not a real project, nor an example of a bad project, just a poor final report. Methodology : The project board met quarterly and formed working groups around MIS data validation, ontology development and project testing. This board was serviced by the Project Officer (grade 5, 0.9FTE), who also had oversight of the project working group, which consisted of the Project Officer, Project Developers 1 and 2, and admin support from departmental staff... Methodology This section gives a lot of (mainly unnecessary) information on project management activities, but nothing on the methodology of the project. In this section we would have like to have seen a summary of the overall approach and why it was taken (e.g. why Ruby on Rails was chosen) followed by a description of the methodology in more detail. Outcomes : This project was a complete success. We made presentations at the CETIS Enterprise SIG, prepared a draft SUM for the eFramework and had a paper accepted for a forthcoming issue of the European Journal of Management Processes in Higher Education... Outcomes Apart from not giving information on why this project was a complete success, and why presentations for the CETIS SIG and drafts for the SUM were good for the project, the details given here relate to project outputs, not outcomes of the project. Executive summary : this report details a JISC funded project (under the Tools and Widgets Programme 4/09) which supported holistic modifications of the institutional MIS /VLE interface based on using a Ruby on Rails SOA tool (ASSPOO) combining APIs from external resources with departmental student data. The tool is available online along with the source code and limited documentation. The development of the tool, which is now used in both the Department of Cephalopod Behaviour and the Research Centre for Semantic Modelling, has allowed us to prepare a draft SUM for the Framework.
      • Executive summary
      • Take a few minutes to read this summary. Then ask yourself the following questions:
      • What did this project do?
      • What are the achievement highlights of the project?
      • What were its aims and objectives?
      • What was its main findings?
      • What are its conclusions and recommendations?
    • we asked the programme managers...
      • What would you like to see in a good final report?
      • real-life examples of benefit realisation
      • user comments
      • information on sustainability or further planned work
      • how were your initial assumptions challenged
      • what did you find didn’t work
      • the project situated in a real-life environment, a problem identified and addressed, and the success of the intervention evaluated.
    • we asked the programme managers...
      • What would you not like to see in a good final report?
      • “ difficult” to read without prior knowledge
      • including sections for the sake of it
      • chunks of the project plan!
      • poor executive summary
      • “ the kind of thing that JISC like to hear”
      • written without a clear understanding of how it would be used.
    • Realising the benefits
      • Need to identify where projects have addressed or contributed to any of the eLearning Programme wider intended outcomes or benefits.
      • Projects will need to describe how the outputs and outcomes of their projects have addressed or contributed to these.
      http://www.jisc.ac.uk/whatwedo/themes/elearning/programmeelearning.aspx The vision is of a world where learners, teachers, researchers and wider institutional stakeholders use technology to enhance the overall educational experience by improving flexibility and creativity and by encouraging comprehensive and diverse personal, high quality learning, teaching and research.
    • eLearning Programme Evaluation Framework
      • The evaluation of the e-learning programme focuses on three key questions:
        • What have we done/built/achieved, to what quality, and how efficiently?
        • What has been learned or confirmed through development activities?
        • How has the learning been acted on or fed back in?
      http://www.jisc.ac.uk/whatwedo/programmes/elearningcapital/evaluation.aspx http://www.flickr.com/photos/beyond_engagement/2865358766/