Organisation

Work/Task Breakdown

STAGE 1:  INITIATION / PLANNING

  • Produce Project Brief
  • Create Working Group
  • Analyse activities

STAGE 2a: BUILD

  • Agree Steering/Governance Group
  • Generate and analyse User Stories - creation of work packages
  • Generate site structure requirements
  • Generate content/process requirements
  • Generate permission hierarchy
  • Prepare build and configuration requirements
  • Review status of existing sites for potential decommission

STAGE 2b:ACCEPTANCE

  • Sign-off User Story work packages
  • Sign-off site structure
  • Sign-off content/process
  • Sign-off permission hierarchy
  • Sign Off training and documentation
  • Sign-off build and configuration
  • Implementation of work packages
  • Implementation
  • Go-live preparations

STAGE 3: DEPLOYMENT

  • Support / Deploy Go-Live
  • Implement on going support arrangements
  • Commence agreed decommission

STAGE 4: CLOSURE

  •   Produce Closure Report
  •    Closure Sign-Off
  •    Closure

 

Resources, Skills and Costs

These are the initial additional days required over and beyond the original 75 days, taking it to 135.

Resources from the following teams are required to deliver this project:

  • Project Services   -  Project Manager                                                                                         40 days
  • Project Services   -  Business Analyst                                                                                        10 days
  • Project Services   -  Programme Manager                                                                               05 days
  • IS - SharePoint Solution Architect                                                                                             05 days

It is anticipated that no additional IS resources will be required. Note:- support is currently unknown, SharePoint provide a level of support and a new administration team within MVM will be identified through the project.

However, there is a significant requirement from staff across MVM - currently members of the working group and new steering/governance group to be defined and confirmed.

Assumptions:

  • Mainly covered by risks. See previous. 
  • No additional IS requirements other than SharePoint.
  • That we can continue to access MVM staff.

Project Governance

Project Sponsor is ultimately accountable for the success or failure of the project.  The Project Sponsor must ensure that the project is focused on achieving its business objectives and delivering the forecast benefits.  The Project Sponsor has to ensure that the project gives value for money and adopts a cost effective approach which balances the demands of the business, users and suppliers.  They should ensure that there is appropriate and effective governance for the project. This governance responsibility cannot be delegated.

The Project Manager has day-to-day responsibility to run the project on and is accountable to the Project Board (steering/governance being created) for the successful planning and execution of the project. They are responsible for ensuring that the project produces the required deliverables within the specified time, cost, quality, scope, risk and benefits, within the tolerances agreed. The University Project Manager will work with any Supplier Project Manager in managing any change requests, issues and risks and produce supporting project documentation during the project lifecycle.

The Working Group represents those groups who will use or gain benefits from the project and must be empowered to make decisions on their behalf. Between them, the PM and Working Group will have overall responsibility for the successful completion of the project deliverables.  

 

Project Stakeholders

Name Business Area Role
Additional stakeholders (see responsibilities for names) MVM Project Working Group (Project Team)
Catherine Elliott MVM College Registrar MVM Portfolio Owner
Claire Bradford IS Applications Service Management Sharepoint Solutions Manager (Project Team)
Elaine Wighton IS Project Services Business Analyst (Project Team)
Jens Brincker User Services Division PM Bioquarter (Project Team)
Jim Nisbet MVM Planning Officer MVMBUS Programme Owner
Mark Hay User Services Division Team Lead Bioquarter
Mike Shipston Dean of BMS, Professor of Physiology Project Sponsor
Muriel Mewissen IS Project Services Portfolio Manager
Paul Clark / Sheila Fraser IS Project Services Head of MVM IT/Portfolio Manager
Paul De'Ath IS Project Services Project Manager (Project Team)

 

 

 

Project Info

Project
MVM Business Process Review for SharePoint Delivery
Code
MVM522
Programme
MVM Business Administration (MVMBUS)
Management Office
ISG PMO
Project Manager
Paul De'Ath
Project Sponsor
Sheila Fraser
Current Stage
Close
Status
Closed
Start Date
08-Aug-2017
Planning Date
30-Mar-2018
Delivery Date
07-Dec-2018
Close Date
02-Aug-2019
Programme Priority
1
Overall Priority
Normal
Category
Discretionary