Develop a prototype that simulates the key functionality of the system, then test and refine it so that it can serve as the model for the next phase of development in Sprint 2.
Figma is used to develop the prototype.
Replace this text with notes regarding the DB design. This is my initial database design linking the users and tasks to make a volunteer. Each user and task will have multiple bits of data attached. The tasks include a signed_up and completed field for the user and admin to track each task.
Replace this text with a description of what data will be input, and where / how it will be obtained.
The end-user will input information about themselves when they are signing up. The admin will be inputting information about the tasks when they want a new one created.
This information will be filled out using a form and submitted to the database
The user can mark a task as signed up or completed (used for personal tracking) and will update the data in the database
Replace this text with a description of the outputs for the system - what types of data will be displayed?
The system will display output data by showing the list of tasks on the home screen, showing a list of tasks along with who has signed up for it on the admin homescreen, the details of each task, the signed up and completed check box next to each task.
Replace this text with a description of how the data will be processed to achieve the desired output(s) - any processes / formulae?
The first stage of prototyping was to explore how the UI might ‘flow’ between states, based on the required functionality.
This Figma demo shows the initial design for the UI ‘flow’:
My client said “It would be easier for the admin to contact each person to remind them about a task they have signed up for and havn’t done it yet when it’s close to the deadline. It could be a good idea to add an admin user list. When the admin clicks on a users name underneath the task it will take them to a page will their contact details and a list of all of the tasks they have volunteered for.”
I listened to my client and added a new page when the admin clicks on a users name. This will show the clients contact details e.g. email and phonenumber, as well as showing what tasks the user has volunteered for. I also realised that there was no way for the user to signup, so i added a sign up button on the sign in page taking the user to the sign up page.
The next stage of prototyping was to develop the layout for each screen of the UI.
This Figma demo shows the initial layout design for the UI:
I shows this to my client and they said “The website looks nice and is easy to navigate. However it would be better you got rid of the log in and sign up on the top right of the log in and sign up page. it would be easier for the user if there was message underneath saying something like “Don’t have an account? login” and maybe underline it to show the user that they can click on it to take them to the login or signup page.”
I have listened to my client and added the text below the login/signup form, so that the user can easily see it and change between the pages.
I showed this to my client and they said “Its really good but for some reason last time i didn’t notice that there as no home button. It would be good for users to go straight to the home screen from any page, as well as showing the title of the website on each page.”
I listened to my client and combined their ideas. I made it so that when the user clicks on the website name (Gymnastics Nelson) it takes them to the home page.
Replace this text with notes about what you did to test the UI flow and the outcome of the testing.
Replace this text with notes any improvements you made as a result of the testing.
FIGMA IMPROVED INITIAL PROTOTYPE - PLACE THE FIGMA EMBED CODE HERE - MAKE SURE IT IS SET SO THAT EVERYONE CAN ACCESS IT
Having established the layout of the UI screens, the prototype was refined visually, in terms of colour, fonts, etc.
This Figma demo shows the UI with refinements applied:
FIGMA REFINED PROTOTYPE - PLACE THE FIGMA EMBED CODE HERE - MAKE SURE IT IS SET SO THAT EVERYONE CAN ACCESS IT
Replace this text with notes about what you did to test the UI flow and the outcome of the testing.
Replace this text with notes any improvements you made as a result of the testing.
FIGMA IMPROVED REFINED PROTOTYPE - PLACE THE FIGMA EMBED CODE HERE - MAKE SURE IT IS SET SO THAT EVERYONE CAN ACCESS IT
Replace this text with a statement about how the sprint has moved the project forward - key success point, any things that didn’t go so well, etc.