Skip to main content

Reboot: three years on

I've decided to revive this blog, after a three-year hiatus, to post news and thoughts about my current role as Head of Development Services, in the IS Applications Division, at the University of Edinburgh.  My aim is to give some visibility to what goes on "behind the scenes" (or should that be "behind the screens"?) and to reveal the sort of issues that face IT in a Russell Group university.

My current job is quite different from my previous role at the National e-Science Centre, which was the topic of the previous incarnation of this blog.  Some issues, such as virtualisation and cloud, are common to all IT jobs these days, but the emphasis of my current job is on support and administration systems rather than research.  One important difference is that I must stress that all the posts here will not represent the official position of the University of Edinburgh in any way.

To start off, let me point you at an interesting comparison of the "student experience" at three European universities.  This posting doesn't mention IT at all - which is a little humbling.  On the other hand, perhaps this is how it should be.  People come to university to learn, not to use the IT.  People tend to notice IT most when something goes wrong, so no news can be good news.   Thanks for Guillermo Rein for noting this via LinkedIn.
http://nickybartlett.blogspot.com/2012/01/per-usual-i-must-give-recap-of-my.html .

Comments

Post a Comment

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...
Post a Comment
Read more

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...
2 comments
Read more

"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...
3 comments
Read more