Team Deliverable 1
This is a bout building the skeleton of the Functional Prototype and building the interaction flows or ‘click streams’
Provide your Project or Design Brief of your team project
Background
Collect previous material your team gathered (see Appendix) and summarise what is relevant to this project. If you do not have it yet, provide new work on
Ethnographical data
Provide a Context analysis of the data from your contextual enquiry. Consider the main themes you found, eg People wanted utility, or an informative site. Then consider some aspects you can design for, eg the UX they want to achieve that goal, the sort of task they want to do, the number of steps to do that and any other feature they want
This is another way of generating user stories, so fill in the categories of responses you got
User Experience
Task types
Duration
Other aspects
Utility
Informatiion
Outcome focused
Proto-personas
Risks
Based on the design stage only. However also consider feasibility of your design to be developed in the future. Discuss any issues and research needed to prove the design is feasible
Measures of success for your app
What are you looking for (consider your context analysis)
Product Canvas
Provide a mental model of your system in a diagram. You can adapt this to be more visual if you wan. You can use excel table provided or image below
Prototype Wire Frame
Your wireframes for your design for the rest of the semester, to be improved and expanded. Link to this that is accessible to anyone with link
Heuristic or UX Evaluation of these
No videos required, just evaluate the prototype for your next improvement and summarise the types of issues found
Implementation Plan
In the sheet provided
Appendix:
Team Role
What is the role you will take in the team, what are your main skills you will contribute
List of Roles:
- Content Strategist
- Myself
- Visual Designer
- Limin
- UX Researcher
- Andrew
- Front End Developer
- Limin
- Interaction Designer
- Dylan
- UX Lead
- Andrew + Dylan
These are the designated roles we have chosen, some are shared due to the nature of the role, but all roles can ask for assistance at any time if needed as our team consists of people with a range of skills and experience in different roles because of previous group work.
Team Meeting
When will you be meeting each week and for how long
Example one that might work (change as needed)
Write your availability here:
Meeting Location
Day
Beginning & Ending Time
What will be discussed
Microsoft Teams (Video Call or Chat)
Monday
2:00pm – 4:00pm, if needed can be until 5:00pm
Update progress on upcoming due work for the week / further weeks.
Microsoft Teams (Video Call or Chat)
Thursday
After Lecture
2:00pm – 4:00pm, if needed can be until 5:00pm
Recap on Lecture materials, begin working on new work (if applicable)
Microsoft Teams (Video Call or Chat)
Saturday / Sunday (Depending on availability of Team – not strict, availability is flexible so can’t set definite date)
12pm – 7pm, pick a suitable time on the day as availability is flexible & meeting may not be required.
Update progress on upcoming due work for the week / further weeks.
Collect all your:
1. General observations – contextual enquiry.
2. Storyboards and the tasks that were covered
3. Decisions made to select stories for prototypes
4. Prototypes and ones that were chosen for heuristic analysis
5. Heuristic analysis and generated list of aspects to improve or keep
- Provide wireframes of your design as is.
- Provide the link to your Documentation and make sure the link is accessible to anyone with the link.
- Provide ethics application and information sheet as separate files if needed
- Provide a presentation eg slides of your work with
- What you have improved
- Why you improved this -important
5. If you need to pre-record the presentation of your work
Youtube presentation speech of the work. i will read the speech on the video presentation