Skip to main content

Time to say "thank you"

When writing this blog, I'm always tempted to write about a current project, or a new IT technology, or some aspect of the service we provide.  This belies the fact that a lot of our job is about people, whether they are the people who use our systems, the people we work with in other parts of the University, or the people in our own teams.  One of the most important aspects of my job is to support my staff as they do the actual development work.  As development staff, we tend to immerse ourselves in the current interesting (or frustrating) problem, then the next project.  We focus on how we can improve systems, or processes, or ways of working.

That is why this week I organised a small social evening to say a personal "Thank you" to everyone in Development Services for the work they have put in over the past year.  This was a time for looking back rather than forward, for considering the whole rather than the part, and for taking stock.  More prosaically, it also brought together all three teams - Software Development; Configuration; and Development Technology.  Although team members work together on particular projects, we don't do very much as a whole section; I'm minded to do some more events that bring us all together.

The start of semester may seem an odd time to celebrate the past year, but for Development Services this is actually a reasonably quiet part of the year.  Our most frantic period is before August, when we have to finish all new systems for the next academic year; then of course we have people's summer holidays, so early October was actually the first suitable time to bring everyone together.

People seemed to enjoy the event.  Our parents taught us to say "please" and "thank you"; these phrases are appreciated in the workplace as much as in the home.




Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

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…