Evaluation Matt Shreeve 29 July 2009 Relationship Management Programme Meeting.

Evaluation

Matt Shreeve

29 July 2009

Relationship Management Programme Meeting

www.curtiscartwright.co.uk CC394P003 – 0.1 / Slide 2

What is evaluation?

• Collecting evidence…

• Reporting success…

• Doing research…

• Reflection…

• Identifying lessons…

• Confirming benefits…

• Specific to your project and its success


Why evaluate?

• Your funding agreement tells you to!

• Improve your chances of success

• Reporting becomes easier

• Sell your achievements to your institution

• Learn from your experiences

• Funders like it


Evaluation at many levels

• Project and programme-level

• Formative, summative, etc


A note on “failure”…

• Projects might not meet their original aims…

• … but new learning or lessons is always a success


Project self-evaluation

• Projects conduct their own self-evaluation

• You are responsible for this!

• Evaluation plan in project plan

• Final report

• Completion report

• Advice and support is available from Paul and team

• You can ask me too!


Programme-level evaluation

• Evaluates the programme, not your projects

• Based on your information


Programme-level evaluation timeline

CRM

SLRM

Support, Analysis and Synthesis

Now Sept 2010 Post-project

Formative evaluation: C+C

Post-summative updates:

C+C and BCE evaluation team

Formative evaluation: Support, Analysis and

Synthesis project

Project

Su

mm

ati

ve

eva

lua

tio

n:

C+

C


What do you need to do?

• For the programme-level evaluation

• Nothing yet!

• For your self-evaluations

• Refine your plans, get started and get feedback


Where to get help

• Paul and his team

• Each other!

• Me

• JISC project management handbook

• www.jisc.ac.uk/proj_manguide.html

• Section 16 of the Project Management Guidelines

• Six Steps to Effective Evaluation


The six steps

1. Identify stakeholders

2. Describe project and understand programme

3. Design evaluation

4. Gather evidence

5. Analyse results

6. Report findings


The six steps take you through a process

www.curtiscartwright.co.uk

Example: HYpothetical Project for Evaluative Reasoning (H.Y.P.E.R.)

• Outputs

• CRM process maps between Dept A and Dept B

• Plan for future cross-departmental CRM

• Case study

• Final and completion report

• Evaluation plan

• End of project debrief

• Peer review of outputs

CC394P003 – 0.1 / Slide 13

www.curtiscartwright.co.uk

H.Y.P.E.R. (2)

• Actual desired outcomes

• Close collaboration between Depts A and B

• “Business” culture to better exploit partnering opportunities

• Evaluation plan

• Question: Are Depts A and B ready to work more closely together?

• Methods: Interviews and focus groups

• Timing: Start, middle and end

• Additional benefits

• Staff engagement in overall progress

• Improved understanding at start

• Progress check halfway through

• Can easily report at end

CC394P001 – 0.1 / Slide 14


Top tips

• Refine but don’t perfect your plan

• Try to be self-critical

• Flag up "issues“

• Private channels if necessary

• Be descriptive and prepare to reason why


More top tips

• Talk to others

• Sharing benefits you all

• Accumulate evidence as you go

• Use your blog postings


Key messages

• Consider what project success means to you

• Understand how you will know you’ve achieved success

• Be assured in the above


Thank you for listening…

• Contact me

• 01483 685027 or [email protected]

• In confidence, if necessary

Evaluation Matt Shreeve 29 July 2009 Relationship Management Programme Meeting.

Documents

Transcript of Evaluation Matt Shreeve 29 July 2009 Relationship Management Programme Meeting.