JISC Programme Meeting

Attended the JISC programme managers meeting today with John. As usual the Sarah’s team put together a well organised and structured day, with good food and space to socialise. The theme for this meet was change management and how this impacts on the structure of the evaluation plan. A particular emphases was again placed on the need for base-lining, particularly form the perspective of stakeholders and their expectations. I found the presentations interesting and informative.

Peter Bullen (University of Hertfordshire) a critical friend, gave a presentation on the CABLE project, developed to support change at a local level using the HEA’s SOME NAME  methodologies. The point I particularly liked here was the inclusion of student representatives within the teams instigating the change process. This is something we should possibly consider, once we have a first cohort going through the PC3 process. While capturing the student perspective is part of the evaluation process,  having live input during the revision process might be very beneficial.

Several models of change management and assessment were also presented. As table teams, we  were asked to consider our current institutional environment form several  perspectives and identify the types of strategy that might support the changes required by the project. This was a very debatable topic, and John and I found that we had fairly different views. However this does highlight the importance of role and experience based perspectives. While it is not possible to accommodate all (a most frequently quoted phrase) the more you are aware of the more likely you are to be able to adjust to those that become barriers to change.

The final exercise of the day (other than a quick cluster debriefing) was to consider the project stakeholders. This was facilitated by a very handy set of documents that I think might be useful for us as a team to consider at our next meeting. Several issues/considerations were raised during this. The difference between the requirements from a stakeholder’s role and their requirements as an individual were raised during our tables discussion. This was brought up in light of the prospect of an individual changing jobs, which also reflects on the risk analysis. Another issue discussed and also highlighted by other groups, was where to draw the line regarding which stakeholders to include within the projects process. This becomes a particular issue when stakeholder views/requirements change frequently, and in effect pull the project in directions others than those intended. As with most things these issues are not new nor unique, and require a balanced approach and well documented justification for the decisions taken.

All in all a good day.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: