Skip to main content

"Just enough" Enterprise Architecture

I spent an informative and enjoyable day with a proto-community of people pursuing Enterprise Architecture in UK Higher Education.  Many of the participants had been previously involved in JISC projects and have enjoyed similar events in the past, so I began the day as a bit of an outsider.  In the University of Edinburgh, our progress in adopting "architectures" is mainly on the IT side, via our Applications Architecture and our use of Service-Oriented Architecture.  Enterprise Architecture would integrate all this IT activity with the business processes and goals of the University (or what I sometimes call the administrative processes, for those readers who are unhappy with calling a university a "business").

I've tended to be a little sceptical of fully-fledged enterprise architecture (EA) because it sounds like a mammoth undertaking and the organisations doing it have often been very large corporations.  The two main outcomes of the JISC experiences are that you can do "just enough" enterprise architecture[1], and the creation of a flexible open source tool that does much of the work of the rather expensive commercial offerings[2].  This makes the approach seem potentially applicable to our institution.

There are certainly elements within the general "EA" space that I very much want to engage with.  Side conversations today included how to set up and manage registries of data & interfaces, what works for programme governance and project approval, how to track benefits back to project outcomes, how to engage senior management, and how to demonstrate the value of architectural initiatives.  Some of these I can contribute to even while I am a neophyte with EA "proper".

By the end of the day, the proto-community was beginning to shape into a proper community.  A core group will take this forward while the rest of us contribute via a wiki and mailing list.  The aim is to share the leadership; so some people might lead activities in some areas while being recipients of infomration in others.  This suits my position quite well, so I will do what I can to try and make this a reality.  In the meantime, I have some useful contacts to follow up regarding some immediate issues. 

All in all, a very useful day.  Thanks to LJMU for hosting us.

[1] "Just enough" enterprise architecture means what it says - just enough for a single project, or a single business area, without having to map the entire enterprise.  Which makes "enterprise architecture" a rather misleading title for the set of techniques and principles to map and align business and IT processes, but it wouldn't be the first time that a grandiose name has concealed a useful set of practices.

[2] The open source tool is Archi - an implementation of the Archimate modelling standard.  Archi has been used in a number of successful HE projects.  


Rose Green said…
Hi Dave! Really good to meet you, yesterday. I have seen the model proposed - start with a small, 'determined' group and draw others in as you go along - work in a different context, so I'm feeling very confident that the EA CoP will get off the ground. R

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 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…