User Testing and Stakeholder engagement

[Edward-Nivison]

In our schedule for this semester we have user testing coming up. This will require us to have sufficient documentation, communication through our client with potential users in the future, and to run a demo for them in the coming weeks. This will mean that we need an usuable demo that we can show and have them provide feedback. Anonymously if needed.

I will comment what issues should be created for this and you can click on the dots to create a new issue referencing the relevant comment.

[Edward-Nivison]

Backend: Clear documentation or images showing what each part of the fitness function does for the user to see what is happening.

[Edward-Nivison]

Frontend: Have everything in a working state. You should test with new data to see that it works. Try and get any reflections on it completed as soon as possible (such as the colour thing).

[Edward-Nivison]

Documentation: User documentation on how to use the frontend, how the backend algorithm works, what kind of authentication you could expect to have. Some examples, pictures, video links, whatever we need to make the documentation as clear as possible for the user on how to use our product. However, it should not be overwhelming paragraphs on paragraphs. Have simple short steps that they can follow that are not confusing and so that they do not have to come back everytime. This is something that we should master by the end of the semester and make edits to along the way.

[Edward-Nivison]

Client/Stakeholder communication: We need to communicate when we can demo this to them and also create feedback forms on what we can improve, what they like, etc.

[Edward-Nivison]

@alexdboxall @matthewcawley02 @sineeha-Kodwani @mazfil @RachelCaoCC @Hexuan-Meng and myself. We need to have something by week 6 to demo, this means also organising prior with Belinda (client) about a meeting in week 6 with some other soco staff members. We need to run a demo, have some form of supporting documentation, and preferably something that we could setup on the computer there to show, but if it is something that we have for them to try on our devices that might have to do.

[Edward-Nivison]

Update on the user testing, we have an organised meeting with stakeholders and client tomorrow morning at 11:30am. We will be running a demo session for them to try out themselves, have a go, and ask any questions on it. We are mostly testing the functionality of the front-end, what isn't intuitative, and what we can include in any user documentation to use our product. We will be collecting feedback in a constructive manner towards the end and during the user testing. This is likely just one of many that we perform with key stakeholders over the coming weeks as per our scope of the project.

92 and #93

[Edward-Nivison]

We conducted a user testing session last week and plan to do more in the future, you can see the minutes from the user testing here. There are plenty of decisions and reflections to be made from this, and we will write them out from there, but in the meantime, reference this for them!

Decisions and reflections #92 , #93 .

[Edward-Nivison]

We should work on getting some more stakeholders involved, including the shadow team if they are available to do so.

https://github.com/mazfil/lab-allocator/issues/92#issuecomment-2332960449

[Edward-Nivison]

We should be looking at talking with people about the backend.

https://github.com/mazfil/lab-allocator/issues/92#issuecomment-2332983479

[Edward-Nivison]

We will be working with the Shadow team today about user testing. This will just be running through the program and gathering feedback from them.

[Edward-Nivison]

We are doing some user testing today at 2-3pm and also on wednesday at 9-10am

[Edward-Nivison]

User Testing successfully completed, you can view them .