Image: Thumbnail of Report Cover

Download PDFPDF version of guide [3.0MB]

Download PDFPDF of Quick reference card [0.3MB]

Download PDFTips for PDF and HTML versions [0.5MB]

Download PDFWord version of checklists [0.1MB]

4.1 Project sponsor’s role during implementation

During implementation, the role of the project sponsor .33 involves two broad perspectives. These involve being outward-looking – liaison and stakeholder engagement, and inward-looking – oversight of the project. In most cases, the actual work of the project will be done by the project team, with the project sponsor providing leadership and oversight. The project business case will have described these roles, for example in sections dealing with communication, and governance and control.

Liaison and stakeholder engagement

Effective relationships are crucial.

The project sponsor has a responsibility to maintain effective liaison and engagement, at a senior level, with those parties interested in, or affected by, the project. These stakeholders may include:

  • the Minister and the entity executive;
  • the project board;
  • the project team;
  • partners and suppliers;
  • users and beneficiaries of the project; and
  • community or industry groups.

Effective relationships with stakeholders are crucial to successful implementation of projects. An effective relationship:

  • helps in gaining an accurate and useful understanding of the needs and expectations of the parties;
  • provides a sound basis for the commitment of resources needed for successful implementation;
  • provides a basis for open discussion about any changes to expectations that may be forced by circumstances as implementation proceeds; and
  • assists in a productive approach to solving difficulties that may emerge during implementation, or in resolving differences of opinion about directions of the project.

Interviews with experienced senior executives indicated the benefits of:

  • face to face meetings with stakeholders;
  • the continuity of people involved, particularly on the project board;
  • developing strong relationships between all the members of the project board, and a culture in project board meetings of active involvement, openness to hearing of problems, and decisiveness in responding to them;
  • clarifying liaison and communication responsibilities between the project sponsor and the project team, to avoid any overlaps or gaps; and
  • getting specialist assistance with developing, implementing and monitoring the effectiveness of a communication strategy.

Oversight of the project

Continuity of purpose: keep a ‘helicopter view’ on whether the project is on track for the outcomes approved in the business case.

The project sponsor – often supported by a project board - has responsibility for effective oversight of the progress of implementation. Matters requiring attention include whether:

  • product delivery occurs as scheduled to the appropriate quality;
  • business outcomes remain on track to be delivered by the project products;
  • finances – expenditure and savings – are according to plan;
  • staffing – project staff numbers, capability, turnover and morale – are satisfactory;
  • risks and assumptions are regularly reviewed;
  • variations from plan and risk events are identified promptly and responded to effectively; and
  • sound administrative practices – such as requirements for procurement, probity and recordkeeping – are being followed.

Interviews with experienced senior executives indicated the benefits of:

  • independent assurance of status reporting, to help counter: the natural optimism of project teams in reporting; the technical jargon and complexities of ICT; and the risk of an unbalanced focus on some parts of the project;
  • commencing corrective actions to difficulties quickly – when they may be less expensive to fix and before problems begin to proliferate;
  • fostering an environment of first solving difficulties, and then learning from them – to make it easy for the project team to provide early warning of issues;
  • keeping key stakeholders, including the Minister where relevant, informed in a timely and relevant way of any emerging risks to project delivery; and
  • a focus on continuity of purpose – for the project sponsor and project board to take a ‘helicopter view’ of how well the project is tracking toward the business outcomes in the approved business case.
Traffic lights - green green green red

Monitoring: Green, green, green, RED!

“My greatest learning as a member of a major project board was gained, as most lessons are, the hard way. We had an apparently wonderful system of monitoring, with a summary traffic light report on key aspects of the project. Month after month, the status reports to the board showed green lights – not even an amber light. Then, the status report went red all over. The problem was that some hard things had been scheduled late in the project. All the easy things had gone well, but now – quite late in the timetable – the whole approach was in question.

The crucial learning for me was the importance of arranging the monitoring and sequence of activities to give maximum early warning on more risky parts of the project. These risky parts might be some individual component, or an integration issue, an end-to-end processing issue, or about user preferences. Finding and scheduling the risky parts as early as practical will take careful thought by the project team. But it is worth asking for, otherwise you may be in for a big surprise.”

… Agency division head.

33: If the project sponsor delegates aspects of the management of the project, the allocation of the responsibilities described in this chapter between the sponsor and their delegate(s) should be made clear.