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

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

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…

A brief summary of our major initiatives

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…