aim programme & project guidelines greenwich, 4th march 2010 · within the community key...

Joint Information Systems Committee 3/9/2010 | | Slide 1Joint Information Systems Committee Supporting education and research

AIM Programme & Project GuidelinesGreenwich, 4th March 2010

Christopher Brown, [email protected]

Joint Information Systems Committee

Introduction

Access and Identity Management Programme

Funded Projects

JISC Guidelines

– Programme Manager/Project Manager

– Project Documentation

– Reporting

– Communication

Questions

04/03/2010 Slide 2


e-Infrastructure Stack

Network Infrastructure

Data Infrastructure

Compute Infrastructure

Specialised Applications/Services

General Applications/ServicesSecurity Infrastructure

Support Infrastructure

04/03/2010 | Slide 3


JISC Programmes

Network Infrastructure

Data Infrastructure

Compute Infrastructure

Specialised Applications/Services

General Applications/ServicesSecurity Infrastructure

Support Infrastructure

JANET

Research Data Management Programme

Research Infrastructures Programme

Shared Infrastructure Services

Virtual Research Environments Programme

Access and Identity M

anagement Program

me

Research C

omm

unities Engagement Program

me

04/03/2010 | Slide 4


Access & Identity Management Programme

1st Jan 2009 to 31st March 2011

Focus on process, policy and technology, exploring innovative new areas in all three and forming a natural complement to work being completed under the Services banner on the UK Federation

UK Access Management Federation relationship – support and expansion

– looking at how new developments can improve on this service

– how innovation might help increase the uptake of access to resources and information within the community

Key component of many initiatives across JISC - e-learning, repositories, business and community engagement

Funding projects and activities that help to achieve these aims of the programme

– ID Management Toolkit already funded, ends June 2010

– 08/09 Circular04/03/2010 | Slide 5


08/09 Call Background

Preparatory work - building foundations for production systems that universities might adopt in the future

What needs to be done to prepare the sector (universities and Federation) for future developments

Not just about technical development, e.g. a tool (either software or a guide) helping a University adopt something would be better than a new low level authentication engine.

Encourage institutes to realise the importance of AIM

Get institutes to join the Federation and be effective within it

May feed into the UK Federation (core part of what we’re doing)

Looking at things that will affect the UK Federation in 2 – 5 years time

04/03/2010 | Slide 6


Funded Projects

Project Institution Project Manager Duration

eCert Univ of Southampton Lisha Chen Wilson 12 Months

GRAND (GRanularity, Audit, N-tier, and Delegation)

Newcastle University Caleb Racey 15 Months

Identity & Access Management using Social Networking Technologies

University of Manchester

Mike Jones 9 Months

Logins for Life University of Kent John Sotillo 15 Months

A Proxy Credential Auditing Infrastructure for the UK e-Science National Grid Service

Thames Valley University*

Wei Jie 15 Months

04/03/2010 | Slide 7


Funded Projects

Project Institution Project Manager Duration

Retrieval, Analysis, and Presentation Toolkit for usage of Online Resources(RAPTOR)

Cardiff University* Graham Mason 15 Months

Student-Managed Access to Online Resources (SMART)

Newcastle University Maciej Machulak 15 Months

SOFA (Service-Oriented Federated Authorization)

University of Oxford Andrew Simpson 12 Months

Web Services Tiered Internet Authorisation (WSTIERIA)

EDINA National Data Centre

Fiona Culloch 12 Months

04/03/2010 | Slide 8


Programme Manager – Project Manager

The programme manager provides guidance and support to projects, and coordinates their work within the overall programme.

The project manager is the main link with the programme manager and is responsible for ensuring the project is well managed and that core project documentation is submitted to JISC to schedule. They also have an important role in liaising with other projects, managing stakeholders and working with the project team to deliver the outputs and outcomes of the project.

04/03/2010 | Slide 9


Programme Manager

Facilitate a supportive and cooperative environment for projects.

Manage JISC programmes from launch to closedown;

Provide a framework for quality planning and evaluation, dissemination, and sustainability at programme level, and guide projects in developing plans in these areas;

Provide guidance and support for projects within the programme;

Coordinate the work of projects within the programme and across other programmes;

Arrange programme meetings and other events to brief projects and share their results;

Monitor the performance of projects through progress reports, site visits, etc;

Ensure that project deliverables and core project documents are submitted on time and manage the acceptance process;

Collate the learning of projects together with formative programme evaluation so that the progress and impact of the programmes can be monitored and ‘steered' dynamically.

The relationship between projects and the programme manager is one of mutual support and encouragement, to get the best value from the funding given to the JISC community.

04/03/2010 | Slide 10


What to expect from your Programme Manager

Clear communication;

Quick response to queries;

A promise to resolve problems/issues as soon as possible;

Feedback on project plans and reports;

A framework for quality planning and evaluation, dissemination, and sustainability at programme level;

Help in changing strategy/tactics as required by changes in the environment or learning within the project or programme;

No penalties for learning as you go along or for the failure of well-planned and executed initiatives.

04/03/2010 | Slide 11


Project Managers

Abide by the letter of the grant, the JISC Terms and Conditions, and the Project Management Guidelines;

Put in place robust project management procedures and use them to manage the project effectively;

Write a project plan that clearly indicates how the project will achieve its objectives (using the templates provided);

Submit project deliverables and core project documents on time and ensure they meet quality expectations and acceptance criteria;

Keep the programme manager informed, especially about changes, e.g. changes to plan, changes in staffing, or any delays foreseen;

Report problems and issues early. The programme manager can help prevent small problems becoming large ones;

Provide timely formative feedback on ‘how well things are going’, what the project is learning from the experience, and how the project or programme could be improved;

Attend programme meetings and other events indicated by the programme manager.

04/03/2010 | Slide 12


Let me know

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, please let me know why and how you are handling it. If you need help just ask. Projects that don’t deliver can still provide valuable lessons learned. If things are going well and ahead of schedule let me know.

04/03/2010 | Slide 13


Project Documents

Project management guide –http://www.jisc.ac.uk/fundingopportunities/projectmanagement.aspx

Within 1 month– Cover Sheet– Project plan, Work Plan and Budget– JISC Website project page

Within 3 months– Project website at lead institution– *Consortium Agreement (if any)

Progress reports – Default is twice yearly (Brief, Full, Budget Report) – 6 month full progress report by 1 July

Final reports – Draft final report – 1 month before end of project– Final report and completion reports – by end of the project

04/03/2010 | Slide 14

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

http://www.jisc.ac.uk/fundingopportunities/projectmanagement.aspx


Project Websites

JISC web page– overview of project– project proposal– project plan – final reports (when available)– link to project website

Project web page – 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

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.

04/03/2010 | Slide 15


Collaboration & Dissemination

Never too early to think about:

– Effective collaboration with other relevant projects of the AIM programme.

– Identification of relevant dissemination opportunities for the project outcomes (e.g. relevant conferences, workshops, events, etc).

– Ensuring that project outputs and outcomes are of high interest to a wider community.

JISC Comms for help with dissemination and publicity.

04/03/2010 | Slide 16


Resources & Communication

JISC website – Project Guidelines

JISCPM – http://jiscpm.jiscanswers.org/

JISC Infonet (good practice/guidance) -http://www.jiscinfonet.ac.uk/infokits/project-management

AIM Blog – http://aimprog.jiscinvolve.org/ Anything you want on there let me know

FAM Blog – http://access.jiscinvolve.org/

Mailing list – JISC-AIM (coming soon)

Twitter – Tag any tweets about your project #jiscaim

Blog – please blog about your project

04/03/2010 | Slide 17

http://jiscpm.jiscanswers.org/

http://www.jiscinfonet.ac.uk/infokits/project-management

http://aimprog.jiscinvolve.org/

http://access.jiscinvolve.org/


JISC Blogs

04/03/2010 | Slide 18


What next?

JISC Conference 12-13 April 2010

– Id Mgmt Toolkit session

Site visits to each project– Meet staff– Discuss plan/progress– Discuss any problems/issues

JISC Innovation Forum 28-29 July 2010

Programme Meeting (September)– Progress– Presentations/Demos– Share results and knowledge– Dissemination and evaluation– Network

04/03/2010 | Slide 19

Joint Information Systems Committee 04/03/2010 | Slide 20

And now …

Questions?