Skip to main content

Enterprise Architecture at York

Friday last week was a bit different from the usual, as I went down to York to sit on an interview panel.  York are recruiting a full-time Enterprise Architect (similar to the post that Nikki Rogers holds at Bristol) with responsibility for shaping the whole contribution of IT to the university's business and my role was to provide an external point of view.  I was very interested to learn more about their plans and to compare the architecture situation at York with our own experience.

Each of the candidates had to start their day with a ten-minute presentation about how they would persuade senior managers of the benefits of enterprise architecture.  These presentations were interesting in themselves and I may borrow one or two of the ideas put forward. 

Obviously I can't say much about the interviews themselves, but I will say that this is hard role to fill. The ideal candidate would have a breadth of IT experience, ability to engage confidently with senior managers, excellent analysis skills and corresponding good presentation skills.  The successful candidate would need to lead the architecture work themselves, rather than have a team of architects.  So this is quite ambitious.  On the other hand, it would be an excellent opportunity to prove oneself and I think York are right to create a dedicated role.  I look forward to catching up with their progress.

P.S. The evening train back from York provided more entertainment than usual.  The carriage next to mine was full of rambunctious rugby fans on their way to the Calcutta Cup match on Saturday.  They even had a set of bagpipes with which they serenaded each station.  That's the first time I've heard bagpipes on a train.  I doubt the Scottish fans were quite so happy during the match itself, which was dreadful.


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…

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…