Project 1's presentation will focus more on you again, since you will be presenting to judges.
- Talking with Slides: 2 minutes
- Demo: 3 minutes
- Total: 5 minutes
- Dress nicely for this and all final project presentations (last day of each project's time).
- Dress at least one degree more elegantly than you usually dress for class.
- Examples:
- If you wear t-shirts every day, wear a button-down shirt.
- If you wear jeans every day, wear some slacks.
- If you wear sneakers every day, wear nicer shoes.
- All presentations will be done from a staff member's computer, so your slides need to be online.
- PowerPoint files, Keynote files or files of any kind will not be accepted.
- Suggested online slide applications:
You have to update your profile in Ironhack Projects with the links of your GitHub Repository, Deployed Site and the Slides.
- Title Slide (1 slide): your project's name & your name
- About Me (1-2 slides):
- Where are you from?
- What are some interesting facts about you? (hobbies, travels, etc.)
- Project Elevator Pitch (1-2 slides):
- What is your project?
- How will it work?
- Why did you choose it?
- Closing Slide (1 slide): your project's name, your name & a "Thank You"
- Total: 4-6 slides
- Title Slide (1 slide): your project's name & your name
- About Me (1-2 slides):
- Where are you from?
- What are some interesting facts about you? (hobbies, travels, etc.)
- Project Elevator Pitch (1-2 slides):
- What is your project?
- How does it work?
- Why did you choose it?
- Technical Challenge (1-2 slides):
- What was the most important technical challenge you faced?
- How did you overcome that challenge?
- Big Mistake (1-2 slides):
- What was the biggest mistake you made during this project?
- What did you learn from it?
- Demo Slide (1 slide): literally says "DEMO" with a link to your project so you can open it easily
- Closing Slide (1 slide): your project's name, your name & a "Thank You"
- Total: 7-11 slides
- Don't include a slide just for the technologies.
- Don't include any code in your slides. Nobody will read it.
- Don't include a slide for GitHub graphs.
- Don't go into detail about how the app works. Your demo is where you want to do that.
- If you think that deviating from the structure improves your presentation, feel free to do so. This suggested structure is mostly for people who don't know what to do.
- Plan what you are going to demo and practice it on the live site. That way you won't be surprised if something breaks on the live version.
- Deploy early so you can squash bugs. There are always bugs on the live site at first.
- Add link to your live project to your DEMO slide so you can start it smoothly.
- Your app's colors and sizing might look different on the projector. If you think it might be a problem, ask to test it beforehand.
- If you app is on Heroku, refresh it before you present. Otherwise there will be a delay on the initial load.
-
Technical Requirements: Did you deliver a project that met all the technical requirements? Given what the class has covered so far, did you build something that was reasonably complex?
-
Creativity: Did you added a personal spin or creative element into your project submission? Did you deliver something engaging and playable to the end user?
-
Code Quality: Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming?
-
Deployment: Did you deploy your application to a public URL using GitHub Pages?
-
Total: Your instructors will give you a total score on your project between:
Score | Expectations |
---|---|
0 | Does not meet expectations. |
1 | Meets expectations. Good job! |
2 | Exceeds expectations, you wonderful creature, you! |
- Monday, August 26 - 15:00 hrs (short presentation)
- Wednesday, August 28 - 15:00 hrs (final presentation without demo)
- Thursday, August 29 - 15:00 hrs (demo)