This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
/
Week 10 Standup
55 lines (46 loc) · 2.44 KB
/
Week 10 Standup
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
Complete Before Stand Up 2
Finish Low-Fidelity Mockup - Freya & Rory
Competitor Analyse - Jarrod
User Flow Diagram - Freya
Logo and Marketing Style Guide - Sam
2 x Persona - Freya
2 x Persona - Jarrod
1 x Persona - Alexander
Low-fi Mockup user testing - Freya & Rory (Complete 2-3 More Interviews)
Survey Data Analysis - Alexander
For Week 11:
- Finish Low Fidelity Mockup - Rory & Freya - Completed
- Start Framework - Jarrod - Completed
- Google API Integration - Jarrod - Completed
- 3 x User Testing Session Version 5 - Alex
- Finialise User Flow Diagram - Alex
- Style Guide - Sam - Completed
- Finialise Logo - Sam - Completed
- User Testing - Rory & Freya
- Mood Board - Sam - Completed
- Start High-Fidelity Mockup - Freya
--- Stretch goals
Start High Fidelity Mockup - Freya
Keep Adding to the Acceptance Criteria
Finish User Flow Diagram - Freya
Document Results from User Testing - Freya & Rory
Complete Acceptance Criteria - Freya
--- Future Plans
High Fidelity Mockup
Marketing Material
- Poster
- Handouts
Value Proposition Mapping
Problem Space
The main problem that we had during the user testing session was confustion around the functionality of the application and how it will be perceived by the audience. Although the mockups worked well, we struggled to provide a differienting factor to our application compared to other applications of the market. The group deliberated 2 different concepts in which they deliberated and decided upon.
These are the pros and cons of the different ideas.
Booking style and owners set rates:
+ Better for owners and they're the supply side of the app
+ Allows people to book days in advance
- Basically Kerb and we need a point of difference
- Owners can set rates really high which would make drivers less inclined to use it
No booking and pay a rate as you go:
+ Gives the app the control of rates (can still incentivise owners by putting rates up in areas where we need more parks)
+ Makes the app different to Kerb(it's a more agile version of Kerb)
- Have to solve the issue of not directing people to parks that will be unavailable soon
After discussing both ideas the group decided to go with the No booking and pay a rate as you go system that will allow more of a point of difference within the current market. To further develop this idea, we plan on creating a updated user flow diagram and finalised functionality plan to get this idea working for our high-fidelity mockups.