Skip to main content

The role of a project board

On Tuesday morning, I will be convening the first meeting of the project board for our "Office 365 for students" project.  This is the first time I have convened a project board; I'm more accustomed to leading or managing the project team, reporting on progress updates and issues.  As the board convenor, this time it is I who will be receiving reports, offering guidance and checking overall progress.  It promises to be an interesting experience. It is already helping me understand what the members of a board look for in reports and papers.

I should perhaps mention that Development Services are not implementing this project.  As the system is outsourced and in this case all the integration work will be done by the IT Infrastructure division, my section is not directly involved in the project team.

Not all our projects have associated boards.  Many projects have a single sponsor, or are quite small and self-contained.  Boards are needed for larger projects that affect many users across the university. The Timetabling project affects every school and has a board.  The Distance Education Initiative is similarly diverse and has a Steering Group (which is effectively a board), as do the projects for Learn 9 and the Virtual Classroom.

A good project board fills several roles.  The members are less closely involved with the day-to-day work of the team, which allows them to take a broader view of progress and problems.  They represent the project to stakeholders in the wider University, ensuring that the relevant people know about the project and make appropriate provision to adopt the new system.  The board ensures that the project has appropriate staff, resources and structures to deliver its goals, while checking that the work progresses in the desired direction. 

I'm looking forward to seeing, and indeed leading, the work of the board in practice. 

Comments

Popular posts from this blog

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…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…

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…