Skip to main content

Time to say "thank you"

When writing this blog, I'm always tempted to write about a current project, or a new IT technology, or some aspect of the service we provide.  This belies the fact that a lot of our job is about people, whether they are the people who use our systems, the people we work with in other parts of the University, or the people in our own teams.  One of the most important aspects of my job is to support my staff as they do the actual development work.  As development staff, we tend to immerse ourselves in the current interesting (or frustrating) problem, then the next project.  We focus on how we can improve systems, or processes, or ways of working.

That is why this week I organised a small social evening to say a personal "Thank you" to everyone in Development Services for the work they have put in over the past year.  This was a time for looking back rather than forward, for considering the whole rather than the part, and for taking stock.  More prosaically, it also brought together all three teams - Software Development; Configuration; and Development Technology.  Although team members work together on particular projects, we don't do very much as a whole section; I'm minded to do some more events that bring us all together.

The start of semester may seem an odd time to celebrate the past year, but for Development Services this is actually a reasonably quiet part of the year.  Our most frantic period is before August, when we have to finish all new systems for the next academic year; then of course we have people's summer holidays, so early October was actually the first suitable time to bring everyone together.

People seemed to enjoy the event.  Our parents taught us to say "please" and "thank you"; these phrases are appreciated in the workplace as much as in the home.




Comments

Post a Comment

Popular posts from this blog

Project Leadership

When I look back over recent projects that I've been involved in, it seems that one key to making a project successful is having someone on the team who really drives it forward: someone who is invested in the project as a whole and not just their own part in it. We (by which I mean the University's Applications division) have a well-defined project process, with defined roles, required milestones, deployment standards, and so forth.    All these are useful, but if the team doesn't have a leader, it seems a project can lose its way, perhaps not responding to changing circumstances, getting stuck on a technical problem, or not securing a needed resource in time to meet some external constraint. The leader can be any member of the team - it could be a developer, a project manager, or the sponsor, or someone in another role.  A team can include several people who are this committed to the project; it doesn't have to be a single person.   As an example, one of...
Post a Comment
Read more

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...
2 comments
Read more

"That's not Grid!" - A cautionary tale

I don't usually attempt humour here, but see if you like this... Once upon a time, in the far-off world of Computerland, a great guru arose and declared a vision. "I see a future when all computers will be linked together and people will run their programs without knowing which computers are running them. People do not need to know where their jobs run; they just need the results. I call this Grid Computing!" The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said: "Oh great guru! We have implemented your vision. We can run our programs on whichever processor is free at the time, making sure that all programs can run and making best use of all our processors. No longer does one computer sit idle while another one is overloaded. Your vision is a great success!" "No, no, no!", said the guru, "That's not Grid!" The guru exp...
3 comments
Read more