Skip to main content

EDUCAUSE 2012: day one

I'm at the EDUCAUSE conference in Denver, learning about how other universities are using their IT.  This conference is a broad church, covering everything from corporate systems to learning technologies, with sessions on leadership and user engagement as well.  It's a useful forum to informally assess how well IT at the University of Edinburgh compares to other institutions around the globe (particularly in North America).  On the whole, we seem to be pretty good.

The sessions on the first day were a bit of a mixed bag.  Clay Shirky gave a good opening talk about the power of open data in a connected world - the sort of thing he covered in his TED talk but covering more material.  The main point I took from his talk was that you can't judge what value people will put on your data before you make it available, because you don't know who will be interested in it for what reasons.

The best talk was about change management at the University of Kansas.  Which sounds a bit dull from the summary but was really helpful in showing how to engage users in big projects so that their needs are addressed and they are involved in making the projects work.  It's the sort of thing that I've learnt in theory on leadership courses and it was good to see it in practice.

I was disappointed by a session entitled "Making the case for Open Source".   What I was looking for was suggestions on how to judge the impact of adopting various open source solutions, such as the effort needed to engage with the community and feed back local changes and developments.  Most of the session was actually repeated rather old (and flawed) arguments about the advantages of open source; hardly the up to date experience that EDUCAUSE should be presenting.

The last session of the day was so bad that I won't comment any further.

Of course, part of the benefit of conferences is all the side conversations and chance meetings over lunch and after the formal sessions.  It's interesting to hear what choices other people are making regarding the choice of tools, cloud-based solutions, innovative learning technologies, managing operating costs, and so forth.  It all gives ideas and context for the decisions we have to make back home.

Comments

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