Report for March 2014

Report Date
March 2014

 

Report compiled by Adam Wadee/Maurice Franceschi, (IS Apps Programme Manager) 

 

Section One: Programme Commentary, RAG and Resources Update

Section Two: Projects Not Started

Section Three: Projects In Progress

Section Four: Closed or Withdrawn Projects 

Section Five: 14/15 Projects

 

Section One: Programme Commentary, RAG and Resources Update

 

Overall Programme RAG: GREEN

 

 

 Section Two: Projects Not Started

 

Project InfoProject Manager's Commentary
  

 

Section Three: Projects in Progress

 

Project InfoProject Manager's Commentary

TEL012 (AP34-048)

Moodle Upgrade

Compliance

Milestones

Target dateTitle
02-May-2014Build Review
23-May-2014Integration Sign Off
13-Jun-2014Acceptance Sign Off
04-Jul-2014Deployed to Live
25-Jul-2014Close

RAG Status

GREEN

Report by Colin Forrest for March 2014

 

Achievements in Last Period

  • BRD Analysis complete
  • System Design Spec and Implementation plan have been approved.
  • Build in DEV will commence on Monday the 14th of April which is on target

Issues

  • One Drive integration which is a new feature of this Moodle Upgrade may not be implemented due to unknown factors surrounding support impact.
  • No an issue as such but we are remaining with our current infrastructure.  No PHP upgrade.

Next Steps

  • Upgrade goes into DEV and assessed in this environment.

TEL011 (AP34-049)

Next Generation Personal Response System (PRS) - Procurement

Compliance  

 

Milestones  

02-Apr-2014Completion of Tender
26-Mar-2014ITT - Publication - Milestone Suspended
06-May-2014Receive Tender Replies from Suppliers - Milestone Suspended
20-Jun-2014Award Contract - Milestone Suspended
25-Jul-2014Sign Contract - Milestone Suspended

 

RAG Status

RED

 

Report by Maurice Franceschi for March 2013

 

Achievements in Last Period

  • requirements captured

Issues

  • The project has gathered all the requirements and the documentation is ready for Procurement to publish.

    However, a major issue (closely related to the risk raised around budget at the outset of the project) has arisen that puts the status of the project as RED  as project cannot continue and may well be significantly changed in scope or even not longer have a business case.

    SCE College has indicated that they want to move away completely from the use of physical handsets, instead going for a 'virtual solution' that requires students to use their own mobiles (or potentially, supplied mobiles).

    Some in the MVM College also are supporting this, whereas HSS have still to decide any change in their position.

    The primary motivator for this is the cost of the physical handsets.

    The project team was asked to procure within the parameters of a mixed solution (its remit was not to set out business cases for each option), and so a move to a 'virtual-only' purchse would mean not only changes to the requirements, but also a different procurement from Open to Restricted (requiring a PQQ phase) as the number of suppliers would increase.

    The PM's own view is that due to many other risks around going for this new approach, the best option would be to continue with the procurement of a solution that offers physical handsets and own device, and allowing colleges/schools to decide if they want to stop using handsets. A shorter contract period could also be considered.

    However, this issue is for the Project Sponsor Mark Wetton to work through with the Colleges. Wesley Kerr will be meeting various groups and senior managers in the schools over the next week or two and reporting back to Mark on outcomes.

    Meantime, the project team will complete its work and have everything ready to go if the decision is taken to keep to current procurement parameters.

    Any delay makes it increasingly unlikey that we can procure and install a system for start of term.

    However, there is a possibility that a virtual-only option is so inexpensive that a procurement is not required. Whereas the cheapness of any such solution is reflected in the functionality offered is not clear. Certainly, the function-rich solutions demonstrated by the most likely bidders in the current procurement would be unlikely to be successful against virtual only options.

    PM suggests that with some many unknowns and opinions now being thrown into the ring it may be best to suspend the project and wait for a feasability or somesuch study to be done properly by the colleges.

    PM has indicated to programme owner and programme manager that due to the delay, there may be too many days allocated in 13/14 to the procurement and installation projects which could be assigned to other MVM work instead.

    A new milestone for completion of the Tender is now set so we have an end date for the preparation of the procurement documents at least. The remainder are suspended until decision on funding and type of sytem wanted.

    No impact on budget if we stay within current procurement parameters.

    Project Sponsor, Programme Manager, Programme Owner, (there is no Senior Supplier) have been asked to review this PICCL and get back to PM if they do not wish to approve it by 26/3.

Next Steps

  • decision on funding - publish the tender / amend the procurement / withdraw the procurement

TEL013

Learn Automated Failover

Milestones

Target dateTitle
18-Apr-2014End of Planning
02-May-2014BRD Sign Off
06-Jun-2014Design and Build Review
04-Jul-2014ASOR (Acceptance Sign Off)
18-Jul-2014DSOR (Delivery Sign Off)
31-Jul-2014Closure

RAG Status

GREEN

Report by Colin Forrest for March 2014

 

Achievements in Last Period

  • The project has now been scoped to the approval of the project sponsor and IS Apps Team Managers

Issues

  • There was an issue around what an automated failover could be defined as and what deliverables could be put in place with the expecation that they will be delivered as planned. PICCL
  • The project scope could be extended to include Production Management overview time to investigate how Failovers (with all systems in mind) are dealt with and the potential delgation of failover support tasks to assist with out of hours incidents.

Next Steps

  • Planning work will be redone and Analysis will start.
  • The revised and potentially lower budget will need to be approved.

 

Section Four: Closed or Withdrawn Projects

 

 

Project InfoProject Managers Commentary
  

 

 

Section Five: Projects submitted for 14/15 Annual Plan (above draft red line document)

 

Project InfoProject Managers Commentary
Moodle Upgrade (50 days) 
QMP Upgrade (120 days) 
Next Generation Personal Response System (Implementation) (30 days c/o) 
VLE Student Analytics (250 days) 
Online Assesment Evaluations (120 days) 
TELS Management Information (120 days)