WIP II Approval Process (draft)

Owned by Chrissi Dean (Unlicensed)
Last updated: Aug 11, 2015
2 min read

This process is to support and work alongside the WIPII Communications plan.  Any questions please speak to Chrissi Dean (Unlicensed), WIPII Project Manager.

The approval process

  1. Approach developed and agreed within WIPII project team.  Should be discussed with core team throughout development and feedback welcomed. Chrissi to sign off.
  2. Proposals to be reviewed by Nigel (can be tied into a final discussion with the project team).
  3. Proposal then taken to PMO for discussion, and sign off from Madeleine.

 

Approval matrix

Priority

Definition

Decision Authority

Escalation method

Priority 1

Major impact to project or business operations.  If not resolved quickly there will be a significant adverse impact to revenue and/or schedule.

PMO

via project manager

Priority 2

Medium impact to project or business operations which may result in some adverse impact to budget and/or schedule.

PMO/Nigel

via project manager

Priority 3

Slight impact which may cause some minor scheduling difficulties with the project but no impact to business operations or revenue.

Nigel/Project Manager

via project manager

Priority 4

Insignificant impact to project but there may be a better solution.

Project Manager

via project team

The communication process

  1. Major approaches need to be presented to the Senior Leadership Team (SLT) via the Marketing Forum (monthly)
  2. Once presented to this forum, with agreement from Madeleine the appropriate senior management group is informed e.g. Faculty Managers or the CSP Reference group
  3. The final stage is a wider communication to other stakeholder groups which could include:
    1. Student Services and Administration working group
    2. ITS
    3. Wider Comms and Marketing

 

Feedback process

It may be necessary or beneficial to gather feedback into a proposed solution during its analysis and design.  The general process for this is as follows:

  1. Priority of the work should be assessed using the matrix as noted above
  2. Anything at level 4 can be managed at project team level, and the project manager informed for information via stand up, email or other method
  3. Anything of priority level 3 or above needs to be discussed with the project manager formally before feedback is sought.