Skip to main content

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 our senior developers instigated our programme to develop frameworks for APIs and notifications.  In addition to leading the technical design, he explained the vision, and co-ordinated other people's contributions.  The management team supported the work with funds and effort, and other team members played a role, but he was the driver.  When he left the organisation, the programme floundered for a while until a new leader stepped forward.

An example where a project failed through lack of leadership is one that I initiated.  I saw a need to review how our identify management system treats people who have more than one role - e.g. someone who is enrolled as a student and who is also employed by the University.  I got the project set up and kicked off, and then left it to the division's project process - but no-one on the small team really took charge and made it happen.  The project sent out a survey only a week before students left at the end of the year, which was too late to get a decent response.  Resources got called into other projects and the team only completed half the scope before the end of the financial year put an end to the work.  No-one on the team was behaving badly or failing to do the tasks allocated to them, but neither was their anyone who was seeing the big picture and making the project succeed.

It takes time and commitment to make a project succeed, and the way we structure our work can make this difficult.  We allocate people to multiple projects, with the aim on using all of everyone's time as effectively as possible, so that if one project has a delay, others can proceed.  But the result of this is that projects end up competing for priority, and some end up unloved and forgotten.

I think we may do better to put more emphasis on leadership and a making sure that the leader(s) on a project have sufficient time and support to make each project succeed.

(As a reminder, I'm now using this blog for my personal reflection and thoughts.  For official posts, see our blog for Enterprise Architecture at the University of Edinburgh ).


Popular posts from this blog

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-depth discussions about th…

Data governance at the core

Among all the topics discussed at the Gartner Data & Analytics summit, one undercurrent caught my attention.  It came up at least twice, in very different talks.

The first occurrence was in a presentation by an e-commerce company which made all of its data open to all employees and encouraged them to create innovative analyses of that data.  The introduction of the General Data Protection Regulation (GDPR) last year has caused the company to restructure its data platform with stricter access policies, as they can't reasonably make the personal information of all their customers available to everyone in the organisation.

The other time was in a talk by a Gartner analyst, about different data architectures (e.g. data warehouses, data lakes, & data hubs).   In an aside, the speaker remarked that, in the past, IT departments have tended to collects all their data together first and worry about governance later.  He said that design of a data hub should instead start with data …

"No more us & them"

WonkHE recently posted an interesting opinion piece with the title Academics and Administrators: No more ‘us and them’. In that post, Paul Greatrix rebutted criticisms of professional services (administrative) staff in Universites from some academics. To illustrate his point, he quoted recent articles in which administrators were portrayed as a useless overhead on the key tasks at hand (teaching and research).

This flows both ways, as Greatrix himself points out. As Enterprise Architect, I work with Professional Services colleagues and I have heard some of them express opinions that clearly fail to understand the nature of academic work. Academics cannot be treated as if they were factory workers, churning out lectures on a treadmill.

I think these comments reveal a fundamental clash of ideas about how a University should work. Some people who come into management positions for other sectors tend to frame the University as a business, with students and research funders as customers t…