Skip to main content

Growing and changing

I have reorganised Development Services for the new academic year.  Instead of two large teams, one for software development and one for software configuration, we now have five software teams aligned with the main administrative units of the University.  We have also taken on new staff: six new people joined Development Services this month and we have three more on the way.

This is not change for the sake of it, although I do believe in moving people around occasionally.  For one thing, the old structure was becoming too unwieldy, particularly in the student & academic area where we had one dedicated sub-team sharing a manager with the more general configuration team.  To grow the section, we needed more teams and more team leaders.

Another reason for change was to create teams that work closely with particular partners.  The idea is to simplify the scheduling of projects throughout the year, with the team leader and programme leader working together to schedule a steady stream of work.  Also, the developers in each team will build a deeper understanding of their area, which will enable them to build better systems.

I also aim to develop the leadership skills of my more senior staff.  This is perhaps most obvious to outsiders in the appointment of three new team leaders but I also plan to encourage other staff to take leadership roles by establishing technology forums.  These forums will share knowledge of particular development technologies, tools or methods, working across all the development teams and with our colleagues in production management.    To help me further, I have also formally appointed two deputy heads of section.

This reorganisation has been a lot of effort and it is to the staff's credit that they have handled it with no disruption to our ongoing project work.  I really expect this to improve the way we work and I will look to see how our partners react to it.

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…