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

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…