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

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

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…