Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
JISC Project Plan
Project Information
Project Identifier
To be completed by JISC
Project Title
Disseminating Impact from Engagement with User Groups and
Organisations
Project Hashtag
Start Date
23/01/2012
End Date
31/07/2012
Lead Institution
De Montfort University
Project Director
Prof Roger Smith
Project Manager
Dr Elizabeth Lunt
Contact email
elunt@dmu.ac.uk
Partner Institutions
University of Edinburgh
Project Webpage URL
diego.our.dmu.ac.uk
Programme Name
Embedding impact analysis good practice in research using BCE
practitioners
Programme Manager
Simon Whittemore
Document Information
Author(s)
Dr Elizabeth Lunt
Project Role(s)
Project Manager
Date
01/2012
URL
If this report is on your project web site
Access
This report is for general dissemination
Filename
Diego_project_plan
Document History
Version
Date
Page 1 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Comments
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
Table of Contents
NB : This table of contents ‘auto-populates’ - to update the table of contents – place cursor in the
table of contents, right-click your mouse, click ’update field’, select appropriate option
1.
Project Overview ............................................................................................................................. 3
1.1
Project Summary..................................................................................................................... 3
1.2
Objectives................................................................................................................................ 3
1.3
Anticipated Outputs and Outcomes ....................................................................................... 3
1.4
Overall Approach .................................................................................................................... 4
1.5
Anticipated Impact .................................................................................................................. 4
1.6
Stakeholder Analysis ............................................................................................................... 5
1.7
Related Projects ...................................................................................................................... 5
1.8
Constraints .............................................................................................................................. 5
1.9
Assumptions ............................................................................................................................ 6
1.10 Risk Analysis ............................................................................................................................ 6
1.11 Technical Development .......................................................................................................... 6
1.12 Standards ................................................................................................................................ 7
1.13 Intellectual Property Rights .................................................................................................... 7
2 Project Resources ............................................................................................................................ 8
2.1
Project Partners ...................................................................................................................... 8
2.2
Project Management .............................................................................................................. 8
2.3
Project Roles ........................................................................................................................... 9
2.4
Programme Support.............................................................................................................. 10
3 Detailed Project Planning .............................................................................................................. 10
3.1
Evaluation Plan...................................................................................................................... 10
3.2
Quality Assurance ................................................................................................................. 10
3.3
Communication and Dissemination Plan .............................................................................. 11
3.4
Exit and Embedding Plans ..................................................................................................... 11
3.5
Sustainability Plans ............................................................................................................... 12
Appendices............................................................................................................................................ 12
Appendix A. Project Budget .............................................................................................................. 12
Appendix B. Workpackages ............................................................................................................... 12
Page 2 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
1. Project Overview
1.1 Project Summary
The project links Researchers and Information Management Expertise from De Montfort University
with an Impact Analyst at the University of Edinburgh to develop a case study looking at the analysis
of the impact of participatory research in the area of Social Action. It will apply previously developed
impact approaches from the Impact Analyst to analyse and evaluate the impact of the research. The
project includes the development of a DSpace Impact Repository and project blog to support the
analysis and case study development.
This case study will be based within Social Action research, looking specifically at the impact of
participatory research. The key focus of the study will be on analysis of the impact of the uses,
refinement and dissemination of participatory approaches in which the Researchers very
experienced. The aim is to develop a systematic and targeted approach to understanding the impact
of this research within, for example, community groups and networks. This will enable a better
understanding of the impact and naturally enhance the capacity to make an impact in the future.
The impact analyst and researchers will work to apply approaches and processes previously
developed by the analyst to collate, evaluate and understand the impact of participatory research.
The information management expertise will provide support for this process through the impact
repository which will collate the information found and a blog or wiki to enable the discussion and
analysis of the impact. The relevance of the outputs of the MICE project will also be considered,
specifically for use with a DSpace repository as will be set up here.
1.2
Objectives
The aim of the project is to apply impact expertise and processes to an identified research area
allowing the embedding of capability and processes for identifying and articulating impacts further
within the institution and providing a case study for sharing across the HE/FE sector.
The key objectives of the project are to:
 Develop a case study for dissemination across the sector
 Fully investigate and analyse the impacts of the research area utilising expertise and
approaches developed by the Impact Analyst
 Create a support system for Impact at DMU i.e., an impact repository
 Increase exposure of research and impacts, thereby increasing the possibility of further
impact
1.3
Anticipated Outputs and Outcomes
Output / Outcome Type
(e.g. report, publication, software,
knowledge built)
Page 3 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Brief Description
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
Plan
Report
Report
Report/Publication
Knowledge built
Software
Blog
Knowledge built
1.4
DIEGO Project plan
DIEGO interim report
DIEGO final project reports
Case study document
Understanding of the impact of the research analysed
Impact repository
DIEGO project blog
New application on the impact analysis approach
Overall Approach
Strategy and Methodology:
The work of the project is broken into two strands:
 Analysis of the impact of the research
 Development of impact support systems
These strands are to be carried out along side one another through a series of interlinking
workpackages.
The methodology to be followed can be broken down into 3 key steps:
 Discussion – project partners will engage with one another through a series of visits and
conference calls throughout the project period to guide the work of the project
 Analysis and development – the analysis of the impact of the research will be carried out
alongside the development of the repository
 Engagement and case study development – engagement will be carried out with the
research communities at DMU and Edinburgh, and UK HEIs, to enhance the project work and
share the project outcomes in the form of a case study
Scope and boundaries:
The following are out of scope for the project:
 Analysis of the impact of research not belonging to the Project Team members
 A full evaluation of all repository technologies with respect to their use for impact
repositories
Critical success factors:
 Good communication between the project partners
 Development of the impact repository
 Successful application and/or adaption of the impact analysis approach to analyse the
impact of the research presented
1.5
Anticipated Impact
Impact Area
Maintain research excellence
Page 4 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Anticipated Impact Description
Application of the impact analysis approach to a new area of
research. New methods for impact support and specific
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
Be ready for technology needs in
the future
Have a positive impact on wider
society
Maintain research excellence and
have a positive impact on wider
society
methodological and contextual analysis tools for impact
assessment
Development of an impact repository and use of blog for
impact analysis
Increasing the potential impact of the research through a
process of planning, reflecting and learning as knowledge
exchange activities unfold, to ensure they are engaging and
effective, and sharing this process through the project
blog/wiki
Possible future research and knowledge exchange
collaborations between the institutions
Impact Areas : maintain research excellence; maintain teaching & learning excellence; be more effective/save
money; have a positive impact on wider society; be ready for technology needs in the future.
1.6
Stakeholder Analysis
Stakeholder
Facilitation and Synthesis Team
Research staff at DMU
Research staff at Edinburgh
Technical staff (Library and ITMS)
Researchers in the UK and abroad
JISC and related projects
UK higher education
1.7
Interest / stake
Publishers of the project
outputs
Producers of research impact
Producers of research impact
Maintenance of DMU IT
systems and repository
Readers and users of the case
study who must have
confidence in the content as
researchers.
Outputs from the project;
support and approval for the
project. Liaison and coordination
Lessons from project and
outputs
Importance
(H/M/L)
H
H
M
M
L
M
L
Related Projects
Embedding eXisting & Proprietary Learning in an Open-source Repository to Evolve new Resources EXPLORER - De Montfort University
Measuring Impact Under CERIF – MICE – King’s College London
1.8
Constraints



The project is to be completed within the project period – 6 months
The impact analyst is located some distance from the researchers
The technical resource to the project is limited to 6 weeks of work
Page 5 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012

1.9
The impact analyst time and resource is limited to one day per week
Assumptions

DSpace is an appropriate technology for the development of the impact repository
1.10 Risk Analysis
Risk Description
Probability
(P)
1–5
(1 = low
5 = high)
Communication within 1
the
partnership
is
difficult or limited for
some reason
The tools chosen will not 1
prove suitable for impact
analysis
Severity (S)
1–5
(1 = low
5 = high)
Risk
Score
(PxS)
4
4
4
4
Staff involved in the 2
project
may
leave
DMU/Edinburgh
or
become unwell for a
period of time
2
4
Expectations for the 2
project are higher than
deliverable
3
6
Detail of action to be taken
(mitigation / reduction /
transfer / acceptance)
A
clear
communications
strategy will be developed to
manage communications and
maintain regular contact.
The tools chosen have been
shown to be applicable to
similar projects and thus this is
seen as a low risk. Other
approaches will be utilised in
the event of difficulties.
Appropriate alternative staff
will be identified who will be
able to cover, as effectively as
possible, the roles of those
staff who are no longer
available.
A clear, constant flow of
information
will
be
maintained to stakeholders.
The boundaries for the Scope
of the project will be made
clear.
1.11 Technical Development
The impact repository will be developed using the following methodology:
 User requirements gathering
 Development of a repository design including meta-data schema
 Approval of design by project team and appropriate key stakeholders
 Development of the repository using the design and meta-data schema
 Quality control via testing of the repository using the outputs of the project by project team
members
 Modification of the repository as appropriate following testing
 Production of appropriate documentation for the installation and use of the technology by
other parties
Page 6 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
Quality control – testing procedures and change management:
DSpace is an established technology used for repositories. Thus, testing is only required to evaluate
the development of the repository against the design and meta-date schema and its utlisation, not
the underlying technology. Testing will be carried out as follows:
 Outputs of the impact analysis uploaded to repository
 Correct display and access checked
 Look and feel fit to DMU requirements checked
 Review and user testing with key stakeholders
 Editorial checks carried out
Change management (repository development):
 Issues to be raised by the team member to the project manager
 Issues logged by the project manager and passed to the developer/repository manager
 Response returned to project manager with time estimate to resolve
 Changes prioritised by project manager and completed by developer/repository manager as
fits within project time and resources
 Outstanding changes to be completed beyond the project period following standard DMU
protocols.
1.12 Standards
Name of standard or
specification
DSpace
Version
See: https://wiki.duraspace.org/
TechDis
CERIF
Dublin Core (DCMI)
Notes
DIEGO will adhere to the
standards required by DSpace as
are current within the project
period as this is the technology
being used for the repository
DIEGO will follow general
principles of usability and
accessibility, as recommended by
JISC’s TechDis service
1.3
The meta-data schema will be
developed in line with CERIF
where appropriate – this will
maximise future interoperability
See:
DIEGO will use Dublin core as
http://dublincore.org/specifications/ appropriate in the development
of the meta-data schema.
1.13 Intellectual Property Rights
The authors and the host institution will retain the IPR of all outputs including reports and
documentation produced during the project. They will make available all outputs of the project, via
DORA (De Montfort Open research archive) or Open Source principles as appropriate, to the UK HE,
Page 7 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
FE and Research communities in perpetuity in accordance with JISC’s Open Access Policy or Open
Source Software policy wherever possible. According to the conditions of funding, JISC will be
granted a non-exclusive, royalty free licence to exploit the outputs developed during the project
period in any way it sees fit.
Intellectual property rights including copyrighted material developed by project partners prior to the
start of the project will be retained by the partner. They will be used within the project as outlined
in the project plan. Relevant agreements will be put in place at the conclusion of the project for
their use beyond the project period.
Outputs from other JISC projects may be used and adapted in accordance with JISC’s Open Access
Policy or Open Source Software policy where appropriate. DSpace is subject to a Creative Commons
Licence. All adaptations must be shared under the same licence. This will be used where applicable.
Full details can be found at http://creativecommons.org/licenses/by-sa/3.0/.
2 Project Resources
2.1 Project Partners
Research and information support:
De Montfort University
Main contact: Prof Roger Smith – Project Director
Faculty of Health and Life Sciences
Email: rssmith01@dmu.ac.uk
Tel: 0116 257 7109
Impact Analysis:
University of Edinburgh
Main Contact: Sarah Morton – Impact Analyst
Centre for Research on Families and Relationships
Email: s.morton@ed.ac.uk
Tel: 0131 651 1939
As stated in the offer letter the letters of support from the partner institutions will be taken in place
of a consortium agreement.
2.2
Project Management
The project will be managed by a project manager as a series of inter-connecting work packages as
described in Appendix B. These will be incorporated into a project plan compiled by the project
manager and approved by the project director. The timings in the plan will include tolerances.
Day-to-day management of the project will be undertaken by the Project Manager. Project Team
members will report to the PM. This work will include checking progress against the project plan,
risk monitoring and exception monitoring and reporting.
The PM will be supported by the Project Director. The project director has responsibility for
approving project plans and reviewing progress against key milestones. Exceptions which fall
Page 8 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
outside of tolerances will be referred to the project director. The director will be kept up to date by
monthly reports from the project manager.
Project Director: Prof Roger Smith (Health and Life Sciences)
The Project Director is responsible for the overall completion of the project. He is also the project
liaison with DMU Senior Management.
Project Director
Project Manager
Researchers
2.3
Impact Analyst
Repository
Manager
Developer
Project Roles
Team Member
Name
Prof Roger Smith
Project Director
rssmith01@dmu.ac.uk
Tel: 0116 257 7109
~1
Prof Jennie Fleming
Researcher
jfleming@dmu.ac.uk
Tel: 0116 257 7873
~1
Dr Elizabeth Lunt
Project Manager
: elunt@dmu.ac.uk
Tel: 0116 257 7776
0.5
Alan Cope
Information
Management
specialist
Impact Analyst
acope@dmu.ac.uk
Tel 0116 250 6391
0.5
s.morton@ed.ac.uk
Tel: 0131 651 1939
1
Developer
Information
management
consultant
n/a
a.brine@dmu.ac.uk
Tel 0116 250 6123
6 weeks total time
As and when required
Sarah Morton
Developer
Alan Brine
Role
Contact Details
Days per week to be
spent on the project
Training needs:
 Researchers to be trained on impact analysis approach– training to be provided by Impact
Analyst
Page 9 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
2.4
Programme Support
No specific areas for support have been identified.
3 Detailed Project Planning
3.1 Evaluation Plan
Timing
On-going
Factor to Evaluate
Questions to Address
Method(s)
Use
of
impact Is it appropriate? Are Monthly
analysis approach
results being produced? reports
on
progress
On-going Communication
Are all project partners Bi-weekly
aware of progress etc?
meetings via
Skype
Towards Successful
Is the repository fit for Checking
End of development
of purpose?
using
project
impact repository
information
developed
during
project
Project
Success of the Has
the
project Final project
End
DIEGO project
achieved its aims and report and
objectives?
Case study
document
3.2
Measure of Success
Increase
understanding
and
quantity of impact
All project partners
happy
with
communication
Correct display and
access to information
in repository
Successful
development of a case
study
Quality Assurance
Output / Outcome Project Reports
Name
When will QA be
Who will carry out the QA
carried out?
work?
As reports are Elizabeth Lunt
required
Output / Outcome
Name
When will QA be
carried out?
Start of project
Project website
On-going
End of project
Elizabeth Lunt
Elizabeth Lunt
Output / Outcome
Name
When will QA be
carried out?
Impact Repository
Who will carry out the QA
work?
Elizabeth Lunt
Who will carry out the QA
work?
Page 10 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
What QA methods / measures will be used?
Review by Project Director. Acceptance by JISC
What QA methods / measures will be used?
Accessible. Meets JISC requirements. Accepted
by JISC
Project documents available
Website accessible until end 2015
What QA methods / measures will be used?
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
On-going
Elizabeth Lunt/Alan Cope
Project End
Elizabeth Lunt/Alan Cope
Output / Outcome
Name
When will QA be
carried out?
Project End
Case study
3.3
Who will carry out the QA
work?
Elizabeth Lunt/Roger Smith
Checking development of repository against
design and meta-data schema
Successful display and access to outputs in
repository
What QA methods / measures will be used?
Successful development of case study to meet
JISC requirements
Communication and Dissemination Plan
Timing
Project
start
Dissemination Activity
Project Website and Blog
Audience
All stakeholders
On-going
Project Website and Blog
All stakeholders
Purpose
To
provide
information
about project and
regular updates
To
provide
information
about project and
regular updates
To
disseminate
results of project
Key Message
DIEGO is funded,
to promote aims
and objectives,
Information
about the project
and its outputs
and outcomes.
Project
Case study document
All stakeholders
Show success of
End
the project and
how it will benefit
the audience in
the future.
As
and Conference
Library,
Raising awareness Updates on the
when they presentations
and repository
and
project
and
arise
posters
research
outputs.
community
3.4
Exit and Embedding Plans
Project
Action for Take-up & Embedding
Outputs/Outcomes
Project
Reports
and Documents to be made available on
Documents
project website and stakeholders
made aware of availability.
Project Website
Website and Blog to be continuously
updated.
Case study
Action for Exit
Make all reports available
within DORA.
These are
available externally to DMU
Website to be retained with
relevant information for 3 years
after project end.
On-going interaction with project Case study documentation
partners and stakeholders during made available via DORA
Page 11 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0
Project Identifier: DIEGO
Version: 1
Contact: Dr Elizabeth Lunt
Date: 01/2012
development
On-going interaction with users and
stakeholders.
Development of
repository to appropriate design and
meta-data schema for integration
with other systems
Knowledge and learning Dissemination activities during the
from
completing
the project.
Inclusion in project
project
documentation. Participation in RSP
events
Impact repository
Repository information made
available via DORA. Repository
may be publically available if
appropriate
Documents available via DORA
in the long-term
3.5 Sustainability Plans
Project Outputs
Why Sustainable
Scenarios for Taking
Issues to Address
Forward
Impact repository
Will be applicable to Dissemination to relevant HEIs need to be made
all HEIs particularly HEIs. Awareness raising aware of repository
those with DSpace communication.
availability.
Some
repositories
adaptation may be
applicable.
Knowledge
and Applicable to other Dissemination via RSP
Development
of
learning
projects
appropriate
documentation
Case study
Applicable to all HEIs Dissemination via JISC and Making all appropriate
appropriate conferences stakeholders aware
etc
Appendices
Appendix A. Project Budget
Appendix B. Workpackages
Page 12 of 12
Document title: JISC Project Plan Template
Last updated: Jan 2012 – v3.0