Organisation
Work/Task Breakdown
| Ability to bulk create Visitors' computing accounts | Who is involved |
| Analysis to identify range of use cases for Bulk creation | BA/Sponsor/Heads of IT/EA |
| System analysis and design of bulk creation mechanism | BA/Dev Services/Production Mgmt/Service Mgmt/EA |
| Build, testing and delivery of ability to bulk create Visitors' computing accounts | BA/Dev Services/Production Mgmt/Service Mgmt/EA/College staff requiring bulk creation |
| Perform analysis for requested accounts | |
| Mechanism to check if repeat visitor | BA/Developer |
| Mechanism to check if overlapping or duplicate visit | BA/Developer |
| Mechanism to check if already identity with University, eg CESAR account for COL students and to assign this as the identity | BA/Developer/EA |
| Process for managing exceptions when creating bulk accounts (eg emailing requester to advise of repeat visitor) | BA/Developer/Service Mgmt |
| Ability to assign services to be provided to Visitors' computing accounts | |
| Mechanism to define what services the account is to be assigned on creation | BA/Developer |
| Guidance to be communicated to those needing to bulk create accounts on what services can be assigned (updating current guidance to reflect bulk creation) | BA/Service Mgmt |
| Process for issuing credentials | |
| Process to be defined for requester to know when account and services are available (eg in format that enables mail merge) | BA/Developer/Service Mgmt/EA |
| Process to be defined to inform visitor when account and services are available (eg automated mail merge) | BA/Developer/Service Mgmt/EA |
| Ensure that process for ending visit and deprovisioning services is fully in place | |
| Process to be defined to ensure that visitor's services are deprovisioned at the end of the visit (this should already exist but need to ensure bulk creation doesn't interfere with deprovisioning processes) | BA/Developer/Service Mgmt/EA |
Resources, Skills and Costs
College staff
The project will need to work with the Colleges to identify Bulk creation use cases
The college staff will need to test and sign-off the deliverables
IS Applications staff
Effort will be required from Project Services (PM & BA), Software Development, Production management and Service management. In addition input will be required from the Enterprise Architecture team.
Project Governance
This project will follow the standard project governance in Project Services.
Any changes to major milestones (Initiation, Planning, Delivery, Closure) will be approved by the Project Sponsor, Project Team and WIS.
Major milestones achievements and changes will be submitted to WIS for approval/noting as necessary.
Project Stakeholders
| Name | Business Area | Role |
|---|---|---|
| Alex Carter | IS Applications | Head of Service Management |
| Dave Berry | IS Applications | Head of Enterprise Architecture |
| Fraser Muir | CAHSS | Sponsor (Project Team) |
| Gail Devaney | ITI | ITI ENT programme manager |
| Hugh Brown | IS Applications | Production Management expert for VRS |
| Mark Lang | IS Applications | Dev Tech Manager |
| Michael Sun | IS Applications | Software developer expert for VRS |
| Muriel Mewissen | IS Applications | Portfolio Manager |
| Nicola Davidson | CAHSS - COL | DoPs |
| Sheila Fraser | CMVM | Head of IT |
| Stefan Kaempf | IS Applications | Head of Development Services/Production management |
| Stew Wilson | IS Applications | Software Development Manager |
| Susan Cooke | IS Applications | Service Management - VRS lead |
| Susan Ridder-Patrick | IS Applications | Project Manager (Project Team) |
| Victoria Dishon | CSE | IT Liaison Officer |
| Victoria Weinsberg | IS Applications | Business Analyst (Project Team) |
Project Estimations
The estimate at Brief is 40 days, an increase from 20 days at proposal stage. This estimation only covers the work required to the end of Systems Analysis and Design. At the re-estimation checkpoint, if the project moves into Implementation, further budget will be required.