Search This Blog

I'm beginning to wind down for the xmas break - just the Student Systems Board tomorrow, a meeting of the Applications Architecture Governance Group, a review of the first phase of development for the new university web site, then a xmas curry with the web site team on Friday, and that will be me off for a couple of weeks. But before I finish, I want to record some thoughts about our IT Futures conference for 2013, which was held last week.

We started planning this in January, when we were thinking about ideas for a theme and potential speakers. I had the idea of inviting a science-fiction writer to give an outsider's view of what higher education might look like in the future. This was tossed around a bit and Jen Ross suggested Cory Doctorow. Meanwhile, the theme of "disruption" rose to the surface. We put the two together and a potential agenda began to take shape.

The next step was to add a less technical and more people-oriented take on "disruption". For this, the name of Aleks Krotoski was suggested. So we contacted both Cory and Aleks and were very pleased when they both agreed to speak. The Principal, Tim O'Shea, also agreed to give his views of the challenges facing the University. We had a programme.

And on the day it went very well. Aleks actually gave her talk by pre-recorded video and then joined a response / Q&A session via Skype, with Chris Speed engaging Aleks in a discussion about some of the key points; this format worked rather well given the theme of the day. Cory also strayed from traditional academic style, sitting on a table and talking with no need for slides. Our other presenters were more traditional (not being media stars) but made good points.

The only thing that went less well than planned was the audio for the concluding panel. I had suggested that we structure this like a radio chat show rather than a traditional academic panel, to make it more engaging. In terms of content, it worked - the discussion was rather interesting - but unfortunately the audio wasn't up to handling that number of microphones in close proximity and there was rather a lot of interference so that people at the back of the hall couldn't hear the conversation properly.

Overall though it was a very good day and I'm glad to have been a small part of it. I really had little to do with the actual organisation of the event. I'm not being modest - I simply didn't have enough time to devote to this on top of the day job, however much I would have liked to do so. So my thanks to the rest of the team for turning all our ideas into reality.

Get link

Facebook

Twitter

Pinterest

Google+

Email

Other Apps

Get link

Facebook

Twitter

Pinterest

Google+

Email

Other Apps

Comments

Popular posts from this blog

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…

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…

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…

About Me

Work: I am the Enterprise Architect in the Information Systems group of the University of Edinburgh.
Play: I like board games, particularly those in the 18xx family; music, although I don't play myself; and reading, especially science fiction.