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

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…