Skip to main content

Enterprise Architecture at York

Friday last week was a bit different from the usual, as I went down to York to sit on an interview panel.  York are recruiting a full-time Enterprise Architect (similar to the post that Nikki Rogers holds at Bristol) with responsibility for shaping the whole contribution of IT to the university's business and my role was to provide an external point of view.  I was very interested to learn more about their plans and to compare the architecture situation at York with our own experience.

Each of the candidates had to start their day with a ten-minute presentation about how they would persuade senior managers of the benefits of enterprise architecture.  These presentations were interesting in themselves and I may borrow one or two of the ideas put forward. 

Obviously I can't say much about the interviews themselves, but I will say that this is hard role to fill. The ideal candidate would have a breadth of IT experience, ability to engage confidently with senior managers, excellent analysis skills and corresponding good presentation skills.  The successful candidate would need to lead the architecture work themselves, rather than have a team of architects.  So this is quite ambitious.  On the other hand, it would be an excellent opportunity to prove oneself and I think York are right to create a dedicated role.  I look forward to catching up with their progress.

P.S. The evening train back from York provided more entertainment than usual.  The carriage next to mine was full of rambunctious rugby fans on their way to the Calcutta Cup match on Saturday.  They even had a set of bagpipes with which they serenaded each station.  That's the first time I've heard bagpipes on a train.  I doubt the Scottish fans were quite so happy during the match itself, which was dreadful.

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