Skip to main content

Annual Planning and Annual Development Reviews

Over the last month or so we've been busy with our annual planning process. This is when we invite the service owners across the university to put forward proposals for work in the 2013-14 academic year.  Development Services have the task of giving a rough estimate of how much effort might be required for each proposal, so that the service owners, college registrars and heads of support group can decide what would make the best use of our time.

This year we have tried to make the annual planning more "light touch".  For my management team, this means that we have given each project a simple estimate of Small, Medium or Large, rather than trying to assign a precise figure.  This makes a lot of sense, as the proposals are usually quite general at this stage and a detailed estimate would require far more time spent in understanding all the details of the potential implementation.  It also means that we can get the estimates done sooner and produce a first draft of the potential programme in December, two months earlier than last year.  This in turn gives people more time to review their priorities and/or investigate certain proposals in more detail.

One unforeseen effect of doing this planning earlier was that it overlapped with the time when we run our annual development reviews.  So we've been doing two stressful things at once!  If we've been a little harder to get hold of than usual, this is probably why.

Development Services has grown substantially over the last year.  To manage this expansion, we've delegated some of our management tasks to senior team members.  Each is now responsible for one or two other members of the team, taking over the monthly 1-to-1 meetings and the annual reviews.  In addition to making the management practical, this is also giving our seniors a chance to develop their leadership skills.  My impression is that so far this is going well.  We will be reviewing progress in the new year, which should give us a chance to iron out any minor problems that arise.

In the meantime, I wish all readers a Merry Christmas and a Happy Hogmanay!


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…

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…