Project Assurance Resources

Understanding Project Governance

The information in this guide is intended for general purposes only. For more specific guidance around your organisationā€™s projects, please get in touch with our team.

Project governance is one of those necessary business practises that is really only felt when itā€™s not there. While some may find the ā€˜adminā€™ and structure around a project much less exciting than the delivery of the project itself, the lack of effective governance can make it very hard to know where a project is at, and will quickly derail progress when no one is clear as to how to proceed.

In this guide, we talk about what governance for a project involves and why itā€™s so valuable to incorporate to any organisational initiative.

Governance sets the rules of the game (or project)

Launching into a large project (or a small one for that matter) without setting clear expectations and reference points for how it will be run is simply inviting headaches at some point. Most projects that forego or gloss over putting governance in place learn sooner than later that the lack of oversight and support is a roadblock. Usually they end up having to retroactively apply governance principles to keep things together.

So what do we mean by ā€˜rulesā€™? Governance could be described as a framework that informs oversight, reporting, communication, responsibilities and documentation. Governance is less an artefact than it is a set of best practises. By having the approach of project reporting and delivery laid out clearly, there are fewer roadblocks to deal with later.

For example, if the governance process has outlined and circulated who in the business is responsible for certain aspects of signing off the project, including who the escalation points are, the delivery team donā€™t have to worry about who to approach when trying to get milestones signed off. Governance commits every stakeholder to the project in some way.

Project success is much more than delivery teams doing good work. If the lines of reporting and communication arenā€™t in place, how can these teams expect to get buy-in or support through periods of adversity? Effective governance doesnā€™t slow a project down, it empowers it to progress quicker.

IQANZ_blog_Feb2_3

Building your governance structure

Governance over an initiative can be as simple as a Sponsor or senior leader making decisions about the direction of the work, or as complex as a multi-layered decision hierarchy with escalation points and tolerances and sub-groups and a kitchen sink for good measure.

Simple is usually better – we see too many projects with overly complex governance structures which slow down decision making and cause the work to grind to a halt. But we also see projects where governance is absent and people are off working on tangents and the project never really gets delivered.
So the Goldilocks principle applies to your governance – not too much and not too little. A couple of key senior leaders who have skin in the game and can make decisions on behalf of the business is far better than a two-tiered governance and advisory structure with a dozen people who donā€™t really know why theyā€™re there and what decisions they should be making.

Your structure needs a few important things:

  1. Someone who is accountable for the decisions that need to be made to keep an initiative moving forward, and who is senior enough to make those decisions
  2. A small group of some other people who support the someone make those decisions, who are experienced enough to know what kinds of questions they should be asking and answering
  3. An information flow that gives that accountable person and other people the kind of information they need to make the decisions.

Get those things right and you will have an effective governance structure.

Establishing a reporting framework

Having a methodology around reporting is important to keep senior management informed as to the progress of each open project. Reporting frameworks will set out the information that needs to be captured and the frequency at which it needs to be provided to key stakeholders and the leadership team. Reporting is typically a combination of budget, delivery progress metrics and commentary by a project manager, telling decision makers what they need to know about a project to help keep it moving or get challenges out of the way. Reporting structures may require a set of project management, tracking or reporting software tools that allow a shared cloud-based access and easy report generation.

If the steering committee or senior leader responsible for overseeing the establishment of a project hasnā€™t initiated proper reporting structures, thereā€™s no visibility of whatā€™s happening and where the issues may be. Where reporting lacks, information finds other less constructive ways of reaching leadership – often without the context it needs to be acted upon appropriately.

The reporting framework will also determine exactly who is responsible for reporting – this may be split up across different people to feed in information, or there may be a report for the steering committee, who prepare a higher level version for a senior leadership team.

Defining roles and responsibilities within the project

Where the buck stops and who to go to for sign off causes a great deal of frustration in many organisations across New Zealand. This is typically a symptom of not having these responsibilities adequately reviewed and confirmed with each stakeholder. Signing off work is considered a big personal commitment and itā€™s understandable why many stakeholders slow down the process to ensure their name is attached to a deliverable they understand and believe has been satisfactorily completed.

Roles and responsibilities also extend to jobs like reporting, day to project management, steering committee members, programme manager and even those at the executive level who ā€˜ownā€™ the strategic imperative the project is associated with.
Having clear, commonly understood, and well defined roles and responsibilities keeps everyone on point and aligned.

Keeping track of and managing risk to the project

Managing risks is done effectively when everyone understands the risks the project is facing and their role in keeping those risks off the issues list. The risk register is a common tool to do this, but it must be kept up to date, and actively maintained if it is to be of any use. Otherwise, itā€™s just some more paper the project has generated that becomes less and less valuable the older it gets.. While establishing high level risks at the outset is important, this document should be considered ā€˜livingā€™ with new threats added to the register and triaged or addressed effectively.

While an organisationā€™s project management framework might outline what constitutes a risk and how to properly capture it within a risk register, the art of risk management is ensuring risks are owned at the right level and that those with the most ability to mitigate a risk are the ones implementing preventative actions.

Governanceā€™s role in risk management is two-fold – it needs to know what the overall risk profile of a project looks like so that it can understand how much risk an organisation is taking on. But it also needs to be actively involved in avoiding those risks coming to pass. Too often we see all risks in a project owned by the project manager, and itā€™s on their shoulders to manage all the triggering events that lead up to a risk. Thatā€™s lazy governance. The Steering Committee, or Project Board, or whatever the governance group are named, are the people who organisationally have the authority and span of control to mitigate risks. So it needs to be a joint effort between the project teams and its governance to keep an eye on the risks and prevent bad things from happening to the project.

Establishing measures of success

What does progress look like? What will the project manager use to define success? This needs to be set out at the same time or directly after scoping the project. In a complex project, measurements may exist at different levels. The project delivery team may work on influencing a number of measures on a day to day basis that are part of a sprint or module of work. These measures may reflect more granular tasks such as a specific piece of coding in the case of a technology based project. The project managerā€™s own measure may be chunked into general outcomes for each sprint, such as a core functionality of a new platform.

The governance function needs to be clear on what success looks like for the project as a whole. These key performance indicators can include delivery to an agreed timeline or cost envelope (thatā€™s the traditional measure) or achieving the expected level of benefits or stakeholder satisfaction with the project outcomes (thatā€™s a bit more nuanced). Whatever success looks like for an organisation though, that must be defined upfront and agreed, so that the project team knows what theyā€™re aiming for and so that progress can be tracked as the project moves along. And these are not set and forget measures either. Itā€™s governanceā€™s role to continually test the project against the KPIs to ensure itā€™s moving in the right direction, and so that if something goes awry that will impact on success, interventions can be made soon enough to get the project back on track.

IQANZ_blog_Feb2_3

Meeting Cadences

There is no shortage of meetings in a typical project. Daily standups, retros, 1-1 catch ups and weekly team meetings are just some of the meetings that delivery teams will have to navigate. Add a swathe of governance, advisory and stakeholder meetings on top of that and itā€™s a wonder anyone gets any work done!

Good governance wonā€™t just determine a rhythm of meetings that best services the projectā€™s outcomes, but will balance the needs of the project leadership, stakeholder and SLT levels as well to ensure information is shared in an efficient and effective manner. We see many projects where the project leadership team are attending two or three different governance forums throughout a month, each with their own information and reporting requirements. Again, the Goldilocks principle is our friend here. If you canā€™t get away from multiple different governance meetings, at least try to work with your governance members to align reporting needs. The machinery of governance takes a lot of feeding, all of which costs time and money that some projects donā€™t have to spare.

But, if thereā€™s no set pace at which a project presents to its governance group, there can be a huge amount of time between meetings, leaving issues to run longer than necessary and sometimes add undue risk to the projectā€™s success.

Informing the quality assurance approach

Dealing with issues throughout a project is not about avoiding them, but having visibility and plans for them if they do arise. As part of strong governance, risk assessment and mitigation strategies help milestones be set realistically and be met.

Getting in front of threats that could derail completion of a stage of your project may take some more time before the project commences, but the benefits will become quickly apparent when things are kept on track.

Where to next?

Read our other project resources:

IQANZ_blog_Feb2_2

Setting project milestones

Staying on track isnā€™t just a matter of delivering on time, but controlling costs too. We offer some useful tips when setting project milestones.
Learn More >>

IQANZ_blog_Jan2_3

How to avoid project failure

Project failure is something every organisation wants to avoid. We touch on some of the approaches to preventing things going wrong.
Learn More >>

IQANZ_blog_Jan2_1

Identifying project risks

Risks exist in all organisations. Itā€™s how we prepare, adapt and navigate these risks that makes projects successful. Read our guide on spotting and dealing with risks to a project.
Learn More >>

IQANZ_blog_Feb2_1

Understanding project governance

All the structure and processes around how a project is delivered can mean the difference between a successful project or not. Learn what governance is and how it can help.
Learn More >>

IQANZ_blog_Jan2_2

What causes scope creep

Scope creep affects every project manager or project team member at some point in their career. In this guide, we explore what some of the causes are.
Learn More >>

IQANZ_blog_Jan1_4

Managing project stakeholders

In this guide, we offer some tips for managing stakeholders to keep relationships positive and projects on track.

Learn More >>

Latest Project Assurance Articles

Preparing the business for a project

Preparing the business for a project

Perhaps youā€™re a business relatively new to the world of projects. Or maybe the business has gone through significant changes that create somewhat of a ā€˜clean slateā€™, meaning all processes and practices are up for improvement. You could also be an organisation that is delivering projects regularly but have a sense that they are harder to get through than they should be.

read more

Get In Touch

IQANZ Limited
Level 2, PSA House
11 Aurora Terrace
PO Box 11-757 Wellington,
New Zealand

04 473 4340
info@iqanz.com