Final Project Presentation

Guidelines

For your final project presentations, you will use an Ignite format. In an Ignite talk, you have 5 minutes and 20 slides, with the slides automatically advancing every 15 seconds.

We are using th Ignite format to encourage conciseness, clarity, and preparation. It's a fun challenge, like a friendly race against the clock, where you and your team get to showcase your ideas in bite-sized, super-focused snippets. There's always a bit of a thrill (and some laughs) when juggling those 15-second slides. Plus, it's a great way to level up your presentation skills, learn to cut to the chase, and really think on your feet--valuable stuff for your future endeavors!

Overview of the Ignite Format

  • Total Duration: 5 minutes
  • Slide Count: 20 slides
  • Time per Slide: 15 seconds (must be set up to automatically advance)

Suggested Contents of Presentation

Introduction (2 Slides | 30 Seconds)

In the first two slides, introduce your team and provide a project overview (e.g., what is it called, what does it do).

Technical Aspects (10 Slides | 2 Minutes 30 Seconds)

The bulk of the talk should focus on technical aspects of your project, such as the following:

  • Technology Stack: List the technologies (languages, frameworks, tools) used.
  • Design: Discuss how your project is structured and how that design ensures maintainability and parallel development.
  • Key Features: Highlight key features of your project
  • Code Quality and Efficiency: Discuss coding standards, best practices followed, or any efficient coding strategies used.
  • Challenges and Solutions: Describe a major technical challenge faced and how your team overcame it.
  • Future Enhancements: Briefly mention potential future improvements or additions.

Teamwork and Project Management (6 Slides | 1 Minute 30 Seconds)

This section should address topics like the following:

  • Team Dynamics: Discuss how your team worked together.
  • Communication Methods: Briefly outline the communication tools and strategies used.
  • Role Distribution: Explain how roles and tasks were distributed among team members.
  • Conflict Resolution: Share a brief example of a conflict encountered and resolved.
  • Project Management Methodology: State if you used Agile, SCRUM, etc., and how it was implemented.
  • Learning and Growth: Reflect on what the team learned or how you grew from this project.

Conclusion (2 Slides | 30 Seconds)

Use the final two slides to summarize your key points or takeaways from your presentation.

Tips for Success

  • Rehearse Timing: Practice to ensure you can convey your points within the 15-second window per slide.
  • Stay on Topic: Stick to the specifics for each slide to maintain focus and coherence.
  • Engaging Visuals: Use visuals effectively to complement your spoken words (e.g., screen captures/animations, diagrams)
  • Clear and Concise: Be clear and concise in your speech; avoid filler words.
  • Team Coordination: Coordinate speaking roles to ensure smooth transitions between team members.

Evaluation Rubric

Your final presentation will be evaluated according to the following rubric:

1. Adherence to Format (20 Points)

  • Excellent (17-20 Points): Perfectly adheres to the Ignite format, with all slides advancing on time and the entire presentation fitting within the 5-minute limit.
  • Good (13-16 Points): Mostly adheres to the format, with minor deviations in timing or slide transitions.
  • Satisfactory (9-12 Points): Adequate adherence to format, but with noticeable timing issues or inconsistencies.
  • Needs Improvement (5-8 Points): Struggles to maintain the Ignite format, with several timing or transition issues.
  • Poor (1-4 Points): Fails to adhere to the Ignite format, with significant timing or transition problems.

2. Content and Organization (20 Points)

  • Excellent (17-20 Points): Content is exceptionally well-organized, clear, and comprehensive, covering all required aspects as per the guidelines.
  • Good (13-16 Points): Content is well-organized and clear, covering most required aspects, with minor omissions or organizational issues.
  • Satisfactory (9-12 Points): Content covers basic aspects but lacks depth or clarity in some areas, or some minor aspects are missing.
  • Needs Improvement (5-8 Points): Content lacks organization, with several required aspects missing or poorly presented.
  • Poor (1-4 Points): Content is disorganized and incomplete, missing several key aspects of the presentation guidelines.

3. Delivery and Communication (20 Points)

  • Excellent (17-20 Points): Delivery is engaging, confident, and clear, with excellent verbal and non-verbal communication skills.
  • Good (13-16 Points): Delivery is generally good, with clear communication, but may lack a bit in confidence or engagement.
  • Satisfactory (9-12 Points): Delivery is adequate but may lack clarity, confidence, or engagement in some parts.
  • Needs Improvement (5-8 Points): Delivery is weak, with significant issues in clarity, confidence, or engagement.
  • Poor (1-4 Points): Delivery is poor, lacking clarity and engagement, with severe communication issues.

4. Visual Aids (20 Points)

  • Excellent (17-20 Points): Visual aids are exceptionally well-designed, relevant, and enhance the presentation significantly.
  • Good (13-16 Points): Visual aids are good, mostly relevant, and contribute positively to the presentation.
  • Satisfactory (9-12 Points): Visual aids are adequate but may lack in design or relevance in some parts.
  • Needs Improvement (5-8 Points): Visual aids are poorly designed or minimally relevant, detracting from the presentation.
  • Poor (1-4 Points): Visual aids are very poorly designed or absent, significantly detracting from the presentation.

5. Team Coordination and Interaction (20 Points)

  • Excellent (17-20 Points): Team shows excellent coordination and interaction, with seamless transitions and balanced participation.
  • Good (13-16 Points): Team coordination is good with effective interaction, though there may be minor issues in transitions or balance.
  • Satisfactory (9-12 Points): Team coordination is adequate, but with noticeable issues in transitions or unequal participation.
  • Needs Improvement (5-8 Points): Team shows poor coordination and interaction, with awkward transitions and unbalanced participation.
  • Poor (1-4 Points): Team coordination and interaction are very poor or non-existent, severely impacting the presentation.

Additional Note

  • Based on peer reflections and contributions to deliverables (GitHub commits, presentation participation, etc.), the instructor reserves the right to score each team member differently on the project. This approach ensures fair assessment of individual efforts and contributions to the project.

Submitting Your Work

Your work must be submitted Anchor for degree credit and to Gradescope for grading.

  1. Make a recording of your presentation and upload to YouTube. Ensure that your upload is accessible (though it may be marked as unlisted).
  2. Navigate to the appropriate Gradescope link
  3. Enter the URL of your YouTube video into the form and submit.
  4. Upload a copy of your recorded presentation to Anchor using the form below.

Note: Anchor submissions can occur at any time during the term, but it is critical that you upload all of your work to Anchor before the last day of the term. Gradescope submissions must be submitted before the deadline (or the late deadline, if applicable).