Overview
Background
A review of the online student experience, conducted by Headscape in the spring of 2016, highlighted many examples of poor user experience (UX) arising from a lack of user-centred design, inconsistent standards, and lack of integration between services. The insight provided by the study showed that the overall online experience provided by the University is substantially below student expectations.
A significant contributing factor to the current situation is the lack of user experience-related skills and processes with the University’s planning and development practices.
The Digital Transformation programme will raise the level of skills and awareness of UX practices among staff across all disciplines involved in software procurement, development and service management, both within IS and across all areas of the University that collaborate in the provision of a digital experience.
Scope
- This project will outline the requirements for defining the process around extending the existing EdGEL to support all users with a cohesive experience of Edinburgh University as a Digital Entity. It will investigate and communicate the benefits and opportunities for using the GEL and will engage users across the University. It should be noted that engagement will not stop with this project but will continue in other projects.
- This project is about understanding the gaps between what exists in EdGEL as it currently stands and what will be needed to extend the service throughout the University.
- It will review the current EdGEL website with proposals for improvement
- The outcomes of this project will feed into DTI008
Not in Scope
- The actual delivery of a process. We are only defining processes in this project.
Objectives & Deliverables
The deliverables are prioritised using the MoSCoW prioritisation method:
M=Must Have; S=Should Have; C=Could Have; W=Want
- (M= has to be satisfied for the final solution to be acceptable in terms of delivery dates, compliance, viability etc.
- S= high-priority requirement that should be included if possible -workarounds may be available
- C= a nice-to-have requirement
- W= want but will not be part of this project)
Objectives and Deliverables |
Priority |
Owner |
O1 To define a framework for delivering EdGEL as a Service (EaaS) for the University |
|
|
D1. A defined EdGEL process includes Insights report as an appendix |
M |
Karl Smith |
D2. EdGEL Website Update review and proposal |
M |
Karl Smith |
D3. EdGEL Website Update |
S |
UWP – Billy Wardrop |
D4. An EdGEL Interaction Style Guide 1.0 |
M |
Karl Smith |
D5. Harmonise results with DTI008 |
M |
Karl Smith |
O2 To create an engagement strategy which will investigate and communicate the benefits and opportunities of EdGEL |
|
|
D1. Engagement strategy | M | Karl Smith |
D2. EdGEL adoption strategy backlog document |
M |
Karl Smith |
|
|
|
O3 To make the case for continuing EdGEL for BAU funding |
|
|
D1. Initial Recommendations for a Service Management model including plans, processes and estimates of ongoing BAU costs to feed into DTI008 |
M |
Karl Smith |
D2. Gap Analysis |
M |
Karl Smith ISG Dev |
Benefits
The benefits from this project will be:
- We will be able to make initial recommendations on how to move forward with delivering EdGEL as a Service
- We will have raised awareness around the University of the benefits and opportunities that come from using EdGEL
- We will have delivered reusable engagement support tools, not just engagement itself
Success Criteria
- The development of a framework that identifies the gaps to be filled in order to introduce the EdGEL service throughout the University.
- The EdGEL Website has been reviewed with proposals for change.
- Initial engagement with the University communities through workshops and stakeholder engagement, giving us a baseline from where we can introduce measurement.
- A first draft of process guidance materials are available for use. These guidance materials will be taken forward and developed further through future iterations outwith this project.
- Recommendations have been made making the case for BAU funding.
- Adoption strategy backlog created
Project Milestones
Planning |
24-Mar-17 |
Recommendations to continue EdGEL |
30-Jun-17 |
Framework for delivering EdGEL |
30-Jun-17 |
Engagement strategy initiation |
7-Jul-17 |
Delivery – all tasks completed |
17-Jul-17 |
Close |
26-Jul-17 |