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!

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…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …