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

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 …

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…

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…