Your presentation will be given to your instructors, fellows, and other students, and should last around 5 - 7 minutes. This is not a long time at all!
We will do the presentations in batches of 5. The first group of 5 teams will present to each other in the main Zoom room while the second group stays in their breakout rooms and works on updating their team's README.md to explain what Grace Shopper is. We will then swap over, so that the first group will go into their breakout rooms to work on their README.md while the second group presents to each other.
At the end of this process every team will have presented their project, seen 4 other teams present, and have a complete README.md that explains to any person who stumble across your project on github what it is, and how to clone it down and run it. Other additions to your README.md could include design choices, how you implemented various features (e.g. the cart for non-logged in users), screenshots etc. The idea is that if a potential interviewer goes to your github to look for your code, they will see your README.md and know that you are a smart, thoughtful programmer and team player.
Everybody in a team should speak at some point in your presentation. Here is what we would like you to cover:
Show a single basic & fast run-through of your application from first-time visitor to ordering a product(s). Highlight what is unique about your application and thoughts behind the decisions made regarding features and user experience (includes visual structure and design). We recommend having demo screens / tabs already set up so you do not waste time, e.g. typing in long forms.
The expectation for these sections is to show and talk about code.
We presume you put your own spin on Grace Shopper, whether that is a whole new feature or an ad-hoc code approach. What challenges did you encounter? How well did your codebase cope? How could it be implemented differently? What decisions did you make while planning and/or working on it?
Select a component of your codebase that you consider to be implemented well. What qualities did you consider in your selection and how does this component reflect those qualities? Is there anything unique to this component that happened in the process of planning/coding that contributed to its quality?
Knowing what you know now, if we could go back in time to last Monday, what would you have done differently? This includes code-specific challenges and challenges in planning/team coordination.