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

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