Grace Shopper Presentations

gspresentations.md

Presenting Grace Shopper

Presentation Overview

Your presentation will be given to your instructor and assigned fellow, plus any other available staff. It will include a general overview / demo of your application followed by various code-focused sections. The whole presentation should last no more than 11 minutes. Practice beforehand to calibrate how much time that is!

General Application Overview (~2 minutes)

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.

Code-focused (~9 minutes)

Each member of your team should be responsible for presenting one of the following. The expectation for these sections is to show and talk about code.

Important! You will be talking about your WRITTEN CODE for the following sections.

Implementation of extra or unique features (< 2 minutes)

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?

A proud part of your application (< 2 minutes)

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?

Under construction (< 2 minutes)

Select a component of your codebase that you believe was not implemented quite as well, and could use/will require some future work. What characteristics did you consider in your selection and how does this component reflect those characteristics? What are the long term effects to your codebase/application if this component remains unchanged?

Your best test (< 2 minutes)

Select a unit test you've written that you consider important/high-leverage to your application. Why do you consider this an exemplary test? What was your thought process in deciding what to test and how to test it? Discuss the long term effects to the codebase due to the existence of this test. When will this test have to change and will it change easily?

Do over (< 1 minute)

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.