Connected Devices/Projects/Smart Kitchen: Difference between revisions
(lean start up flow) |
(team) |
||
| Line 232: | Line 232: | ||
== Team == | == Team == | ||
* [mailto:thills@mozilla.com Tamara Hills]- Project Lead | * [mailto:thills@mozilla.com Tamara Hills]- Project Lead/SW Engineer | ||
* [mailto:nicoletti@mozilla.com Russ Nicoletti] - SW Engineer | * [mailto:nicoletti@mozilla.com Russ Nicoletti] - SW Engineer | ||
* [mailto:cserran@mozilla.com Candice Serran] - | * [mailto:cserran@mozilla.com Candice Serran] - EPM | ||
* [mailto:nyee@mozilla.com Nicole Yee]- EPM | * [mailto:nyee@mozilla.com Nicole Yee]- EPM | ||
* [mailto:dbialer@mozilla.com David Bialer]- Product Manager | |||
* [mailto:kevin@grandon.org Kevin Grandon] - SW Engineer Contributor | * [mailto:kevin@grandon.org Kevin Grandon] - SW Engineer Contributor | ||
Revision as of 20:43, 29 July 2016
| Project Smart Kitchen |
|---|
|
|
| Author(s) |
| Mozilla |
| Released |
| 06.08.16 (Initial Pitch) |
| Innovation Status |
| Stage 1 (Validation) |
| Website |
| TBD |
Smart Kitchen is a project that addresses the need for anyone who needs to eat--which is all of us! Throughout this project, we are exploring what it would be like to know what is in your fridge all the time with little to no effort. Then after knowing the ingredients is in your kitchen, being able take those ingredients and suggest new and healthy recipes to try. To do this we are utilizing image recognition technology to scan food items and bar codes.
Project overview
Smart Kitchen is a project that attempts to help people answer the question "What's for dinner?" in such a way that optimizes ingredients on hand, reduces food wasteage, and offers recipes (eventually) tailored to the user's time, skill, dietary requirements, allergies, likes/dislikes, etc.
Problem Hypothesis
We believe that there are people who are responsible for creating or managing meals for 2+ members of their household
… who have difficulties coming up with ways to combine their existing kitchen inventory for a proper meal because
…they want to sit down as a family and eat a proper dinner together.
We will know this to be true when we see evidence from the research study.
Product Hypothesis
We believe that people who are responsible for creating or managing meals for 2+ members of their household
… are currently addressing it through eating out, and eating frozen meals and cooking the same thing repeatedly
By building the SmartKitchen service that provides meal options based on existing food inventory
…we will provide more options for meals and therefore making it easier for people to have more family dinners.
We will know this to be true when we see feedback from users from a prototype indicating it was helpful.
Initial Prototype
For the initial prototype of the Smart Kitchen project, the goals are the following:
- Understand the capabilities and gaps in the combination of Visual recognition and barcode reading for use in determining a kitchen inventory.
- Using user feedback from testing we want to understand the usefulness of such a service. We also want to drill into the key user barriers to making the service helpful.
Lean Start Up Flow
Vision Statement
SmartKitchen aims to answer the question "What's for dinner?"
Ideas
- Use image recognition to identify the inventory of the kitchen
- Use barcode to identify and manage the inventory of the kitchen
- Use RFID to identify and manage the inventory of the kitchen (entire house, garbagecan)
- Use OCR to identify and manage the inventory of the kitchen
- Use the inventory of the kitchen to provide recipes
- Use an Open Source Cookbook to provide recipes from the community and socially engage/gamify the community in the food area
Leap of Faith Assumptions Being Tested
- We are assuming that we can use image recognition to accurately identify some percentage of the contents of the kitchen
- We assume that people want recipes that they can make with their existing kitchen inventory
Experiments
- We believe that if we give a user an experiment device for identifying their inventory that we will be able to recognize 20% of items with our existing training to date.
- If run a Facebook Ad describing our product, we expect a 2% response rate
- If we create a video that shows our product vision and advertise it, we expect a 2% response rate.
Experiment Details
- Details on all experiments can be found here
Program Status
| Milestone | Date | Status | Status Notes |
|---|---|---|---|
| Passed Gate 0 | 06/08/2016 | Done | Gate 0 Pitch |
| User Research Survey | 06/10/2016 | Done | user Research Doc |
| Kick off in London | 06/13-17/2016 | Done | |
| Prototype Requirements Document | 07/13/2016 | Done | Prototype Requirements Document |
| Problem/Product Hypothesis Building | 07/07/2016 | Done | Problem/Product Hypothesis |
| Participatory Design | 07/12/2016 | On Hold | Participatory Design Template |
| Lean Start Up Training | 07/13-14/2016 | Done | |
| Experiment #1: Prototype | 07/15/2016 - 08/08/2016 | On Target | Experiment Details |
| Experiment #2: Video | 07/15/2016 - 08/12/2016 | On Target | Experiment Details |
| Experiment #3: Facebook Ad | 07/27/2016 | Done | Experiment Details |
| Experiment #4: Facebook Refactor | 07/28-29/2016 | Done | Experiment Details |
| Hypothesis Validation Prototype | 08/04/2016 | On Target | Smart Kitchen Prototype Requirements |
Status Key
| Color | Status | Key |
|---|---|---|
| On Target | The project or deliverable is expected to meet its due date. | |
| Challenged | The project or deliverable is facing an issue that might cause it to miss its due date, but a “get well” plan has been developed to get it back on track. | |
| At Risk or Late | The project or deliverable is blocked or facing an issue that might cause it to miss its due date, and there’s no “get well” plan to get it back on track, or it is already late. | |
| Done | The project or deliverable has been completed. | |
| On Hold or Not Started | The project or deliverable has either not been started or has been placed on hold. |
Sprint Demos
| Date | Video Recording | Overview |
|---|---|---|
| 07/01/16 | Sprint 2 Demo | Image recognition with IBM Bluemix and bar code recognition. |
| 07/08/16 | Sprint 3 Demo | MySQL Database, checking in the schema, connecting to the data, and identify items user flow. |
| 07/15/16 | Sprint 4 Demo | Hardware: LED lights, enclosure and stand, button,
|
| 07/22/16 | Sprint 5 Demo | Inventory to Recipe flow, Google Analytics and metrics |
| 07/29/16 | Sprint 6 Demo | Summary of our findings for the Facebook ad experiment and status update on our video and prototype experiment |
Communication
IRC
Join the conversation on irc.mozilla.org, channel #SmartKitchen.
Vidyo
| "SmartKitchen" Vidyo Room |
|---|
|
Hello,
|
Bi-Weekly Sync Ups
The Smart Kitchen has open bi-weekly sync ups every Tuesday and Thursday at 11:00AM PST in the SmartKitchen Vidyo room. Instructions for joining the video conference (vidyo) meeting room are above. Meeting notes can be found here.
Project Management (Trello)
- Smart Kitchen is operating on one-week sprints. To follow our actions throughout the gating process, please follow our Smart Kitchen Trello.
- We give weekly Demos in the Smart Kitchen vidyo room at 11am Pacific.
References
- Innovation Board pitch deck
- Google Drive folder
- Smart Kitchen Trello
- SmartKitchen Prototype Design Requirements
Team
- Tamara Hills- Project Lead/SW Engineer
- Russ Nicoletti - SW Engineer
- Candice Serran - EPM
- Nicole Yee- EPM
- David Bialer- Product Manager
- Kevin Grandon - SW Engineer Contributor