Skip to main content

New office plans

We have a date for our move to new offices.  On April 18th, most of Applications Division will be moving from Old College to two refurbished floors above the Moray House Library, between Holyrood House and the Royal Mile.  The new space will be better equipped than our rather dated offices and will even include a staff room where people can eat their lunch, a luxury that we currently lack.

The planning has reached an advanced stage.  Last week we reviewed the specs for the audio-visual kit.  Our new meeting rooms will have wall-mounted display screens, which will make a pleasant change from having to book and set up our portable data projector.  We will also be able to use the displays to join video conferencing calls using Collaborate or Skype.

In addition, we will have wall-mounted displays in some of the team areas.  In Development Services, we will use these to show live database and system monitoring, which will help us visualise the behaviour of our servers.  We will also display project information such as burndown charts for Agile projects.

We also checked the furniture manifests.  When we first started to plan this move, the Estates and Buildings unit suggested we move all staff to small desks and sit them in long rows.  This does not work well for development staff: most of my staff have two screen on their desks plus notes and reference books, and they need quiet in which to think.  Fortunately we settled that discussion several months ago.

The last piece of the puzzle is the arrangement for the day of the move itself.  We've been told that we should pack up the day before and come in the day after; the removal company won't want us getting in the way on the actual day.  So we are planning how to use this time.  We may set up team away days or training sessions - these are still to be decided.

Overall, the new offices should be much better equipped.  A bonus for Development Services is that we will all be on the same floor, except for our members of the Student Systems Partnership who are colocated with their counterparts from the Academic Registry.   This will be an improvement from our current situation in which each of my teams is in a different room, on different floors, separated by swipe-card-controlled doors.  The location won't be as grand as Old College and I have yet to work out my cycle route from home but once we're inside the facilities should be much improved.

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…