Prototype Plan
Note: This prototype plan for thesis is in constant iteration. Later tasks for dates to come will be added and current ones edited as needed.
User statement (in development)
V1: A product system including a physical product and digital product to help MS patients communicate with their families and empowering them to improve their communication with the person living with MS.
V2: A physical and digital product to empower MS patients and their family manage MS better.
V3 (and current): A communication device and app to empower MS patients and their families to understand and manage MS better together.
To-do schedule
Feb 11–18
Concept/Prototype
- Update concepts and flows
- Create final user flows of app and physical product
- Finalize content
Other
- Catch up on all blog posts
- Set priorities of what I am building
Feb 18–25
Concept/Prototype
- Build 10 app screens
- Build schematic for physical product
- Complete user journey
- TEST with three users
Other
- Make proof of concept ready — make presentation
- Meet with advisor
What will the proof of concept have?
- Key user app screens and flow — 5–7 screens (high fidelity)
- Mockup (or physical prototype) of how the physical product behaves
- Interaction between physical product and app
- Include key user feedback points (maybe)
- Presentation design and scripting
Feb 25 — Mar 4 Proof of Concept (POC)
Version 1 (POC) can involve substantial mockup, as opposed to working code/hardware. But the walkthrough must be realistic enough and the overall presentation complete enough that users are convinced of the viability of your idea.
Concept/Prototype
- Build 10 more screens
- TEST app and product
Other
- Present proof of concept
- Set up process book document
- Meet with advisor
Mar 4 — Mar 11
Concept/Prototype
- Finalize app screens
- Start building physical product fully
- TEST app and product
Other
- Meet with advisor
Mar 11 — Mar 25
Concept/Prototype
- TEST app screens and content
- TEST physical product
Other
- Brainstorm names for the product
- Make Looks-like Feels like ready — make presentation
- Start building out the process book
- Meet with advisor
What does the Looks-like Feels-like include?
- Finished app flow
- Finished product behavior
- Illustrate interaction between physical product and app
- User feedback and journey
Mar 25 — Apr 1 Looks-Like Feels-Like (LLFL)
Version 2 (LLFL) will require a more complete finished simulation, with clear design choices and interactions refined on the path to actual functionality.
Concept/Prototype
- Iterate after feedback from users and class
- TEST app screens and content
- TEST physical product
Other
- Keep building the process book
- Start building out the final presentation
- Brainstorm names for the product
- Meet with advisor
Apr 1 — Apr 8
Apr 8 — Apr 15
Apr 15 — Apr 22 Looks-Like Acts-Like (LLAL)
Version 3 (LLAL) should be fully functional. The functionality/fidelity timing will vary for each student depending on what you are building.
Apr 22 — Apr 29
Apr 29 — May 6
May 6 — May 13
May 13: Thesis Festival
