Skip to main content

Away Day: Service Management

Every four months, our Division's management team have an Away Day, a chance to concentrate on particular aspects of our work without the distractions of our day-to-day responsibilities.  We don't go very far, just to a meeting room in the University's Salisbury Green hotel, right next to Arthur's Seat, but it is away from our respective desks.

Yesterday we focused on the three year strategy for our own services, the ones run by our Service Management section.  These include the university portal, the web hosting service, the lecture capture service, the VLEs and other technology-enhanced learning tools, the ID management system, the electronic voting system, and others.  The three team leaders from the section presented their plans clearly and their presentations triggered lots of discussion.  We reviewed their plans for making services even easier to use from smartphones and tablets, adding functionality without duplicating effort, and integrating services so that users have the information they want when they want it.

One issue that we returned to throughout the day was the need to engage users in our service plans .  We plan to establish more user groups for our services and to involve these groups in the design aspects of our projects.  As the leader of Development Services, this is something I am very keen to take advantage of.   Close user involvement has been key to the success of our Agile development projects and we could do more on other projects if we could investigate user interface options early on.

From a projects point of view, we also discussed how to run more usability evaluations and to engage service management in the usability and graphics aspects of our user interface design.  From a corresponding service point of view, we discussed how to provide continuous improvement via a range of options, from small enhancements through to making better use of our project planning processes.

There was plenty to discuss and several useful points arose that we will be taking further.  Hopefully this day spent away from the mundane will lead to better services for all our users.


Popular posts from this blog

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.

This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…