Presentation is loading. Please wait.

Presentation is loading. Please wait.

SA&S-Fortnightly Status Report – Overview Period Ending 25 Oct 2017

Similar presentations


Presentation on theme: "SA&S-Fortnightly Status Report – Overview Period Ending 25 Oct 2017"— Presentation transcript:

1 SA&S-Fortnightly Status Report – Overview Period Ending 25 Oct 2017
Deliverables this period WSA : good progress made with appraising system options ahead of the Board SCEC: system workshops completed, team is preparing estimation and release plans. Further process validation planned with academics. MyEd Portal: demo of 1st release to DT Board done, planning its release. Requirements being reviewed. Student UX engagement report written. Exam Timetabling: Test environment & data feed ready for testing by the Exam Timetabling team Comprehensive timetable : formalising report and recommendations for the Board Tier 4 :  development work on the Biometric card information capture functionality completed. BI capability delivered. Policy: n/a. Project being suspended. Work is now required across the SEP Programmes . TOM: final prep for workshops for Immigration, Timetabling & Student Finance. Current Status Previous Status A A Student portal SAS002 Special Circumstances (SCEC) SAS003 Working and Study Away (WSA) SAS004 Exam Timetabling (ET) SAS005 Comprehensive Timetable Analysis (CTA) SAS006 Policy SAS007 Tier4 SAS008 Target Operating Model (TOM) Management and Control Engagement Delivery Planning Resource RAID Costs & Benefits Stakeholders Communications A G -Exam Timetabling: there are MVM exceptions and extra requirements for Resit exams (risk raised) -MyEd- API dependency & QAS Address look up requires update before go live Timelines completed -MyEd pilot; additional developer & UX resource being addressed -additional resource for TOM work being planned RAID log up-to-date for Risks and Issues, Assumptions and Dependencies. Updated as projects progress. Cost forecasts broken down per project. Benefits log completed in PIDs: logged at programme level. Work required on baselining student (and staff) experience being progressed. Planning additional user engagement at projects from Academics (SCEC), . Good engagement with students (SCEC, WSA and MyEd projects). Being done through projects/workshops, programme lead 1:1 and SEP newsletter

2 SAS– Fortnightly Status Report – Programme Risks -Period Ending 25 Oct 2017
Consequences Inherent Impact Residual Impact Residual Prob’ty/ Uncert’y Risk Level Risk Mvt since last mth Current & Management Processes and Mitigating Activities and Future Developments Senior Managerial Responsibility For information TOM- There is a risk that the ISAS team (International Student Advisory Service) do not engage or actively obstruct with discussions in relation to new Student Immigration Service Single Immigration Service is not achieved or moved to a compromise solution 5 4 16 p 1.engage with Alan McKay from Edinburgh Global 2. engage change manager (Taylor Clarke) at an early stage 3. Actively use the HR toolkit 23/10 Update Meet with Lynne Moyes/HR advisor and the ISAS team on 24/10 to discuss HR issues Other option for programme sponsor to engage with the ISAS team Heather Tracey Exam Timetabling- There is a risk of disruption to  MVM exams – those with fixed dates and resits exams, due to exceptions that may need manual workarounds for initial go-live period Extra effort required to support manual workaround in MVM Schools and Exam team 3 15 New risk- -Aug resits- these are best dealt with as a separate additional phase of project delivery , with another iteration of analysis, build and testing to be done in 2018 for Aug resit-Planning required, raise a change control -Exams outwith main exam diets / fixed date exams for MVM require changes to business process first - before project could deliver personalised exam timetables for students taking these exams. These exams are managed locally within schools - Scheduling is done by number of students -Changes to be assessed 1st Scott Rosie

3 SAS– Fortnightly Status Report – Programme Issues Period Ending 25 Oct 2017
Green - Low Not currently impacting the project A Amber - Medium Resolution in hand and is being managed within the Programme R Red – High Immediate escalation is required Issue Description. There is an issue that… Severity Score (RAG) Issue resolution Senior Managerial Responsibility For escalation to programme N/a For information MyEd portal-There is a reliance on a single developer to build the pilot, creating a single point of failure and no cover during his scheduled annual leave. Low Review technical work (due next two weeks) to identify requirements & resources: Mairi/Peter. Plan additional resources. Options are: Short term: secure developer from DTI011 Leigh Gordon. (DONE) -Use third party software to provide resources from November onwards -Involve Tech Leads for peer review: Peter and Mairi-(Done) Iain Fiddes MyEd portal-EUCLID API taking longer than anticipated to put to live & there is a change to the address look up software (QAS) that is required. My Contact Details delivery will be impacted Medium Engage with API PM (Chris Copner) to replan work around new API delivery schedule. Work with Programme Manager to progress with the implementation of MyContactDetails to have it function tested, signed off and rolled over onto MyEd. Richard Scott

4 RAG Guidance Criteria Red Amber Green
Delivery Key deliverables at risk Some risks around delivery On track for delivery Planning No detailed plan Detailed plan in place. Gaps around benefit/key deliverables. Not fully up to date. Covers less than 6 weeks. Detailed, current plan in place covering the next 6 weeks. Resource Significant skills or resource gaps Some gaps All resource in place and trained. RAID No documented risks and issues. Defined process and roles. Clearly defined escalation routes. Risks and issues log actively maintained and reviewed by project team. Costs & benefits Very limited benefit identification/ limited understanding of costs Some gaps in information. Costs fully broken down and information accessible. Benefits documented and logged in register. Stakeholder engagement Very limited identification. No documented plan. Some ad hoc identification of stakeholders. Incomplete plan. Not approved by sponsor. Stakeholder, interest and needs systematically identified. Plan for engaging in place and approved by sponsor. Communications Little current information on website; stakeholders not informed of status Some ad hoc communication. Some information on website Website updated for last completed stage. Stakeholders informed and aware of nest stage plans. Key messages available for last stage. A programme will be assumed to be green initially. It may be red/amber status if 2/8 elements are red or amber. A project is likely to be red/amber if 3 or more elements are that colour. A project is red/amber if 4 or more elements are that colour.


Download ppt "SA&S-Fortnightly Status Report – Overview Period Ending 25 Oct 2017"

Similar presentations


Ads by Google