User Stories
- As a college student living in a dorm, I want to know how to cook, so that I can save money.
- As a busy worker, I want to cook simple meals, so that I can save time cooking and focus on my work.
- As a parent with a daughter with high standards with her food, I want to know what to cook every day, so that I don’t have to be stressed about picking what to cook.
Minimum Viable Product
The Minimum Viable Product of Recipe Grandma is the automatic recipe recommendation tool according to the ingredients input of the users. Based on the collected recipes in the internal database, users will be able to choose from the recommended recipes.
After finalizing the Minimum Viable Product, our team aims to implement Computer Vision techniques to allow scanning ingredients, instead of manually inserting ingredients into the App. Furthermore, to further improve the user-interaction in the App, 'Reviews' page for each recipe will be added for users to share their comments with each other.
@geontackee - Geon Tack Lee @JenniferZheng0430 - Jennifer Zheng @mohammedajao - Mohammedajao @OyungerelA - Oyungerel Amarsanaa @yeonieheoo - Yeonie Heo @NghiaNim - Nghia Nim
This project came to be due to a recognized need amongst the group to be able to quickly assess food options available. It was realized that the inconvenience of figuring out the food items available from raw ingredients proves difficult for daily life for the average person. This compels them to eat out, lower the quality of the food they eat, or not eat at all. This app aims to solve this mutual dilemma we've all faced with a better user experience offered by competitors. Please look at how to contribute.
- Fork the project with your own branch.
- Run
npm installin the back-end and front-end directories. - Set up a mongodb account and follow the back-end instructions to set up your database.
- Run
npm flowon the front-end to confirm there are no errors. - Run
npm run starton both the back-end and front-end in separate terminal processes. - Happy developing!
| Sprint | Scrum Master | Product Owner | Developers |
|---|---|---|---|
| Sprint 0 | Geon Tack | Yeonie | Jennifer, Mohammed, Oyungerel, Nghia |
| Sprint 1 | Mohammed | Jennifer | Geon Tack, Yeonie, Oyungerel, Nghia |
| Sprint 2 | Oyungerel | Nghia | Mohammed, Jennifer, Geon Tack, Yeonie |
| Sprint 3 | Mohammed | Geon Tack | Jennifer, Yeonie, Oyungerel, Nghia |
| Sprint 4 | Yeonie | Oyungerel | Jennifer, Mohammed, Geon Tack, Nghia |
Each team will decide, using whatever decision-making process they prefer, on which two members will fill the initial roles of Scrum Master and Product Owner.
- all team members, including Scrum Master and Product Owner, are also Developers - everyone is expected to do the design and code work in every sprint.
- these roles must shift every Sprint, so each team member should fill each role at least once.
- each team must announce which team members are Scrum Master and Product Owner at the start of each Sprint
#team-recipe-grandma