I imagine you’re wondering where we’ve got to with the Student Dashboard, aren’t you? In my plan of action last blog, I mentioned the stakeholder analysis we are performing, which is an initial part of the agile co-design process we are following.
Our first step was to identify the stakeholders of the Student Dashboard. Any job role in the university that interacts directly with students, or inputs or processes data about students were considered. The result was as follows:
- Academic Tutors
- Central Student Services
- Faculty Student Services
- Senior Tutors
- Module Leaders
- Alumni Office
Next, we set about interviewing these stakeholders, with the aim of determining who they are and the nature of their interactions with students. We also asked them what student information they draw on, and whether lack of access to any data is a hindrance to providing the best possible student experience.
The discussions with stakeholders will enable us construct personas and scenarios, which are an integral part of the agile co-design process and derived from human-computer interaction design theory. These personas and scenarios will be validated by the stakeholders in the next stage of the process.
Through the analysis of these interviews and the data identified by the stakeholders, we have constructed a table of the data required in the Student Dashboard, ordered by how many stakeholders require it. This has enabled us to shortlist the data that is important to the most people, and begin the process of negotiating access to the sources of these data.
I have been asked to introduce myself and the project I am on. Hi, I’m Rikki. I am currently finishing my PhD and working on a JISC funded project called the “Southampton Student Dashboard”. I have blogged a bit before about life as a student, in case you want a sense of my style.
The Southampton Student Dashboard (I’ll drop the “Southampton” from now on) is a project associated with the Southampton Learning Environment (SLE), and aims to provide a single view of a student’s data to both the student and the various members of university staff that interact with that student.
The hope is that the Student Dashboard will provide a more student-centric approach, by allowing anyone dealing with a student to have all of the appropriate information to hand, without having to contact the myriad of existing owners of this data. This will hopefully enhance the student’s experience and improve retention.
We’ve identified a number of challenges that lie ahead for us. Retrieving the data we need to feed the Student Dashboard will involve both social and technical hurdles. There are clearly going to be privacy issues involved with exposing this data, and close attention will be paid to ensuring protecting sensitive information. There will also be the chance to explore some of the ways of exposing different views of the data to different people, depending on their role and relationship to the student.
At the moment, we are meeting with the various stakeholders (student services, academic tutors, senior tutors, students) to determine which data they require in their interactions with students. We are also in discussions with the computing services staff (iSolutions) about how we will actually access the data from the various existing systems.
The following stages will involve more of the stakeholders in a co-design of the system and interface, which will lead to a prototype being constructed and piloted.
It is looking like an interesting project and I look forward to posting more about it on here. Stay tuned!