Organisation
Work/Task Breakdown
-
New developers staff training
-
System analysis, review current change-based events
-
Review downstream systems' requirements: work with CAM and Timetabling project teams to understand their requirements
-
Design API, workflow, error handling, end points
-
Work with IS Apps to ensure the integration with tools such as WSO2 and the architecture fit with the University integration plans, naming dictionary Federated University Data Mode
-
Build API, Peer Review
-
Open access TEST Euclid (Live and Dev sorted during CMS work)
-
Function testing API
-
Test cases with CAM and Timetabling users- use a sandbox to show data are passed to users’ end points
-
Documentation, review Data Access Protocol
-
Deploy API
-
Review integration with downstream users
-
Review benefits realisation
Resources, Skills and Costs
The resources for this project come from within Core SSP team, based on 2 SSP developers for the duration of the project:
SSP Dev = 195 days - Used so far end July: 45 days (incl training new developers), plus Aug-Jan: 5 months & 15 days/month * 2= 150 days
PM 10 days
IS Apps small: EA for consultation only , and Production for releases, Dev Tech to open access of Test environments = 5 days
Total IS budget= 210 days
Additional resources not accounted in budget above:
-
Student Systems reporting manager
-
Student Systems Operations
-
SSP tester
Project Governance
-
Project governance by SSP management team (weekly meeting: sponsor, PM, SSP team leaders)
-
Monthly reporting and meeting for non-project team stakeholders- linked to the SSP management group meeting every 3 weeks
-
Technical governance for opening access/firewall of Euclid Test environments
Project Stakeholders
| Name | Business Area | Role | Communication Plan |
|---|---|---|---|
| Aaron McHale | CAM | senior user |
consult |
| Balasri Gunasekaran (project team) | SSP Dev | Developer |
stand up |
| Chris Giles | SSP BA lead | SSP BA lead |
Weekly governance |
| Craig Warrack | Student records Operations manager, Student Systems | Student records Operations manager |
inform |
| David Ferreira (project team) | SSP developer | Lead developer |
stand up |
| Defeng Ma | SSP Dev | SSP dev team leader |
stand up Weekly governance |
| Franck Bergeret (project team) | SSP programme manager | Project Manager |
stand up Weekly governance |
| Jamie Morton | SAIM student systems | Reporting manager, data protection lead |
consult |
| Jamie Thin | IS Apps | Timetabling programme manager | |
| John Allison | IS apps Dev Services | IS Apps Dev Services |
Consult |
| Lizzie Beattie | Head of Student Record Operations | Project Sponsor |
Weekly governance |
| Luke Manley | SSP | SSP tester |
consult |
| Marianne Brown, Scott Rosie | Timetabling | senior user |
inform |
| Mark Lang | Dev Tech | IS Support |
inform |
| Martin Jones | Enterprise Architecture, IS Apps | Integration architect |
inform |
| Natalia Oleynik (project team) | SSP Dev | Developer |
stand up |
| Seetha Subramanian | IS Apps Application Management | IS Support |
inform |
| Stefan Kaempf | IS Apps director | Senior supplier |
inform |
| Wilbert Kraan | Data Architect | Enterprise Architecture |
Project Estimations
see above, SSP estimations based on effort over project duration, incl new developer training, support from senior Dev