Speculating Presentation - Feedback

[aaleksandraristic]

Feedback from professor and students:

[aaleksandraristic]

By the professor:

I have reviewed your presentation on the "MealTime" project and would like to offer some constructive feedback. Overall, your presentation demonstrated a good understanding of the tools and methodologies you plan to use. However, there are areas where further depth and clarity could enhance your project.

GDPR and CCPA Compliance:

Feedback: It's great to see attention to GDPR and CCPA, but the specifics of how MealTime will ensure compliance beyond user agreements and age verification could be further elaborated. Consider detailing data handling, storage, and user rights management strategies. Also make sure that there is a kill switch if the users do not agree with your conditions and privacy policies.

Development Tools:

Feedback: The selection of tools like Microsoft SQL Server, Slack, Android Studio, Git, and Firebase is well-justified. However, the integration and interaction of these tools within your development pipeline could be more explicitly addressed.

Android SDK Components:

Feedback: You've listed essential components of the Android SDK, but discussing specific use cases within your application for these components (like Firebase and Android Jetpack) would provide more insight into your development strategy.

Firebase as a Backend Service:

Feedback: Your explanation of Firebase's role in authentication and backend functions is good. However, elaborating on the security measures and data handling practices in place when using Firebase would be beneficial. Another option is not to use authentication in the app as I discussed during the presentation.

App Monitoring and Bug Testing:

Feedback: The approach to monitoring and bug testing is comprehensive. However, linking these practices to your continuous integration/continuous deployment (CI/CD) pipeline would illustrate a more integrated development approach.

Coding Standards and Testing Philosophies:

Feedback: While you've outlined coding standards and testing philosophies, demonstrating how these are practically applied in your project, perhaps with examples, would bring more depth to your presentation.

Automated Deployment Pipeline:

Feedback: The inclusion of GitLab and GitHub for version control is noted. Clarifying how you manage and integrate code changes in your deployment pipeline, including branch strategies, would be helpful.

Updated Story Board:

Feedback: This section appears to be underdeveloped. An updated storyboard would offer valuable insights into user experience and interface design. You need to show how users will agree to the privacy policy and the terms and conditions.

In conclusion, your presentation was well-structured and informative. My suggestions are aimed at encouraging a deeper exploration and articulation of how these tools and methodologies are interwoven into the fabric of your project. This will not only strengthen your presentation but also your practical application of these concepts in MealTime.

Presentation: 90 - I think the presentation went well. The team understood the presentation and were able to successfully defend it. Standups: 90 - for the most part your team is on time. There is continuing repetition of the standup with the users. I would like to see how team members are doing different things to a specific issue. Retrospective: 90 - well done.

Overall grade: 90

[aaleksandraristic]

By other students:

I would plan out how you plan to monetize as soon as you can to make sure it fits in with how y'all are structuring the software Firebase says it automatically handles network interruptions. it has cached data that is available when offline and resends anything that was meant to be sent once it reconnects to internet Coding and testing philosophy is good. I don't think creating an account is a bad idea, that way you would have the users emails to send them occasional information like new meals added and maybe if you create another health related app. Although typing email twice to "confirm" it would be tedious, maybe you can send an email confirmation token with a link to verify the email address Have you considered having the grocery list be a scrollable page instead of multiple pages? Like the notes app in your phone where you just scroll down to see the rest of the note or list. When it says "2 tbls of garlic" and the price, is the price for what you are actually buying? Like the little glass jars that hold 4 tbls of garlic, is the price for the jar you buy, or you have to buy the jar at $5 but the app says you'll be spending $2.50 for this meal? Just curious on how that works.

---

I wish PowerPoint made image uploads more clear because we've had similar issues. From the first slide I think the retype email might not be necessary. I think the main screen buttons like "Generate My Meal" could be made to look more minimalistic and have the size/positioning adjusted to look cleaner. The screen with Baked Salmon is great but I think in the Bookmarks screen you wouldn't need to change the pages at the bottom and instead you could scroll down. "My Grocery List" information could be displayed to look more organized somehow, maybe like: :white_large_square: Chicken 1lb $8.99 :white_large_square: Steak 1lb $13.99

[bdshanks-28]

Thanks, this is some really good feedback actually.