Skip to main content

EA at the University of Lincoln

Last week, Allister Homes from the University of Lincoln gave a presentation to the UCISA EA group about how Lincoln have set up their Enterprise Architecture practice and where they are now in using Enterprise Architecture. The presentation is online and you can see it here:

Enterprise Architecture at Lincoln

Do take a look. 

I found Allister's talk both interesting and reassuring.  Lincoln's EA practice is 12-18 months older than ours, and as a result it is a bit more embedded into university culture and processes than us, as one might expect. But we're on a similar path and not too far behind.  EA seems to be delivering good results at Lincoln, which bodes well for us.

Both practices are based in our IT departments and are reaching out to the business areas.  We are working with similar principles (because we both used the same set of TOGAF principles as our starting point).  Lincoln have an established design authority which reviews all projects; we have put in place processes that do the same and are planning to create a formal design authority.  Lincoln have a set of architecture requirements that all procurements and developments must adhere to; we have a similar set of standard procurement questions, which we are about to review and formalise further.

Allister has made good use of the BizzDesign modelling tool.  We are just in the process of finalising our choice of modelling tool.  We're a bit behind in developing EA models but people are seeing the benefits of those we have produced.  Getting the tool and repository in place will accelerate us down this part of the EA path.

The occasional meetings and presentations run by the UCISA EA community are a really useful way of sharing experience and information among UK universities.  I recommend joining the mailing list if you are at all interested.

Comments

Popular posts from this blog

Project Leadership

When I look back over recent projects that I've been involved in, it seems that one key to making a project successful is having someone on the team who really drives it forward: someone who is invested in the project as a whole and not just their own part in it. We (by which I mean the University's Applications division) have a well-defined project process, with defined roles, required milestones, deployment standards, and so forth.    All these are useful, but if the team doesn't have a leader, it seems a project can lose its way, perhaps not responding to changing circumstances, getting stuck on a technical problem, or not securing a needed resource in time to meet some external constraint. The leader can be any member of the team - it could be a developer, a project manager, or the sponsor, or someone in another role.  A team can include several people who are this committed to the project; it doesn't have to be a single person.   As an example, one of...

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...

"That's not Grid!" - A cautionary tale

I don't usually attempt humour here, but see if you like this... Once upon a time, in the far-off world of Computerland, a great guru arose and declared a vision. "I see a future when all computers will be linked together and people will run their programs without knowing which computers are running them. People do not need to know where their jobs run; they just need the results. I call this Grid Computing!" The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said: "Oh great guru! We have implemented your vision. We can run our programs on whichever processor is free at the time, making sure that all programs can run and making best use of all our processors. No longer does one computer sit idle while another one is overloaded. Your vision is a great success!" "No, no, no!", said the guru, "That's not Grid!" The guru exp...