Skip to main content

Rounders in the park

Yesterday evening a group of us assembled on the Meadows and proceeded to play rounders for 90 minutes.  We were a mixture of people from Applications Division and from the University Web Site team, all involved to some extent in our investigation of the Drupal CMS.  As we work in different buildings, some 15 minutes walk apart, we rarely all congregate and our project manager decided that a social event was in order.  As we all turned down his offer of golf, rounders was the preferred option.

I've been to many team social events in my life but I don't think I've played rounders since I was at school.  It was fun.  After 90 minutes, several of us were beginning to ache and we gladly retired to a nearby restaurant.  My legs still ache today.

What does this achieve, from a work point of view?  Well, at the most basic, it help to puts faces to names.  More than that, it helps us to work together, because we've played together.  We learnt a bit about each other, which makes it easier to start conversations.  And it will help us handle disagreements, because we will know that we have things in common beyond the issue at hand.

I'd be interested to hear of other activities that people have tried for team social events.

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…