H M < M
CMU597: Industry Project - Lecture 12

Final Presentation Sprint

Part A: Assessment Criteria | Part B: Practice Presentations

James Williams

Birmingham Newman University

jwilliams@staff.newman.ac.uk

3-hour session • 2 parts • Final practice!

Session Timeline - Final Session!

Part A: Assessment Criteria & Final Preparation (90 minutes)

30 minutes: Presentation assessment criteria breakdown

45 minutes: Task 1 - Final presentation polish

15 minutes: Break

Part B: Full Run-Through Demos (90 minutes)

60 minutes: Each team presents (15 min presentation + feedback)

20 minutes: Task 2 - Final technical fixes

10 minutes: Closing remarks and good luck!

Learning Objectives

  • Understand how presentations are assessed
  • Deliver polished technical presentations
  • Demonstrate working software effectively
  • Answer technical questions confidently
  • Handle presentation nerves and mistakes gracefully
  • Give and receive constructive feedback
  • Complete final system validation
  • Celebrate team achievements!

How You'll Be Assessed

Total: 100 points (Presentation: 40 points, Project: 60 points)

Assessment Components:

Component Points What's Assessed
Presentation 40 Clarity, structure, demo, Q&A
Technical Implementation 30 Code quality, architecture, features
Documentation 15 README, architecture docs, code comments
Team Process 10 Git usage, collaboration, agile practices
Professional Standards 5 Ethics, accessibility, security

Presentation Assessment Rubric

Criterion Points What We're Looking For
Structure & Clarity 10 Clear intro, logical flow, effective conclusion
Technical Explanation 10 Architecture, tech stack, decisions well-explained
Demo Quality 10 Working demo, smooth execution, shows value
Delivery & Teamwork 5 Professional, confident, equal participation
Q&A Response 5 Thoughtful answers, technical understanding

Technical Implementation Assessment

Criterion Points What We're Looking For
Functionality 10 Core features work, meets requirements
Code Quality 8 Clean, readable, well-structured, DRY
Architecture 6 Appropriate patterns, separation of concerns
Testing 4 Tests written, critical paths covered
Error Handling 2 Graceful failures, user-friendly errors

Documentation & Team Process Assessment

Documentation (15 points):

  • README (6 pts): Clear setup instructions, features listed, tech stack explained
  • Architecture Docs (4 pts): System diagram, component descriptions
  • API Docs (3 pts): Endpoints documented with examples
  • Code Comments (2 pts): Complex logic explained

Team Process (10 points):

  • Git Usage (5 pts): Meaningful commits, branches, PRs, code reviews
  • Agile Practices (3 pts): Sprint planning, retrospectives documented
  • Collaboration (2 pts): Equal contributions, team coordination

Professional & Ethical Standards

Assessed Elements (5 points):

  • Security (2 pts):
    • Passwords hashed, not plaintext
    • Input validation (SQL injection prevention)
    • No secrets in Git repository
  • Accessibility (2 pts):
    • Alt text for images
    • Keyboard navigation works
    • Sufficient color contrast
  • GDPR Compliance (1 pt):
    • Clear privacy policy
    • User data deletion capability

Common Presentation Mistakes

❌ Avoid:

  • Reading slides word-for-word
  • Going over time limit
  • Too much technical jargon
  • Code walkthrough instead of demo
  • Unprepared for questions
  • One person dominates
  • Apologizing excessively
  • "This doesn't work but..."

✓ Do:

  • Speak naturally, make eye contact
  • Stay within 15 minutes
  • Balance technical & accessible
  • Show working features
  • Anticipate & prepare answers
  • Everyone presents equally
  • Focus on achievements
  • Show what DOES work

Managing Presentation Nerves

Normal: Everyone gets nervous! Even experienced presenters.

Strategies:

  • Practice, Practice, Practice: Confidence comes from preparation
  • Arrive Early: Test equipment, get comfortable in space
  • Breathe: Take deep breaths before starting
  • Start Strong: Memorize first 2 minutes cold
  • Focus on Content: You know your project better than anyone
  • Remember: Audience wants you to succeed!
If You Mess Up: Pause, breathe, continue. Don't dwell on mistakes!

Final Pre-Presentation Checklist

Day Before:

  • ✓ Full team run-through with timer
  • ✓ Demo tested 3+ times successfully
  • ✓ Slides finalized (no last-minute changes)
  • ✓ Backup screenshots/video ready
  • ✓ Q&A preparation reviewed
  • ✓ Everyone knows their part

Day Of:

  • ✓ Test demo on presentation computer
  • ✓ Slides load correctly
  • ✓ Internet connection works (if needed)
  • ✓ Water bottles available
  • ✓ Team ready 10 minutes early

Task 1: Final Presentation Polish

Instructions (Work in your project teams):

  1. Review Rubric (10 min):
    • Check presentation against assessment criteria
    • Identify weak areas to strengthen
  2. Refine Presentation (20 min):
    • Improve weak slides
    • Add missing elements (technical explanation, challenges)
    • Ensure equal participation clear
  3. Test Demo ONE MORE TIME (10 min):
    • Run through demo script
    • Fix any last issues
    • Verify backup ready
  4. Prepare Q&A (5 min):
    • Review likely questions
    • Ensure everyone can answer about their part

Time: 45 minutes

Deliverable: Presentation ready for final practice run

Break Time

15 Minutes

Take a break. Next: Practice presentations!

Part B: Full Team Presentations

Part B: Full Run-Through Presentations

This is it! Final practice before the real thing.

Format:

  • Each team presents for 15 minutes
  • 5 minutes of Q&A from class
  • 5 minutes of constructive feedback
  • Treat this like the real presentation!
Purpose: Get comfortable, receive feedback, identify final issues.

Giving Constructive Feedback

Feedback Structure:

✓ Effective Feedback:

  1. Specific: "The architecture diagram on slide 5 was really clear"
  2. Actionable: "Consider adding a slide about error handling"
  3. Balanced: Positives + Areas for improvement

❌ Avoid:

  • Vague: "It was good" or "I didn't like it"
  • Personal: "You talked too fast" → "The pacing was quick in the demo section"
  • Only negative: Always include positives!

Receiving Feedback Gracefully

How to Respond:

  • ✓ Listen: Don't interrupt or defend
  • ✓ Note It: Write down actionable points
  • ✓ Thank Them: Appreciate the feedback
  • ✓ Ask Questions: "Can you clarify...?"
  • ✓ Reflect: Is this feedback useful?
Remember: Feedback is gift! Use it to improve.

Task 2: Practice Presentations & Final Fixes

Instructions:

  1. Team Presentations (60 min):
    • Each team presents (15 min)
    • Class asks questions (5 min)
    • Feedback from peers and instructor (5 min)
  2. Incorporate Feedback (10 min):
    • Quick fixes to presentation based on feedback
    • Only critical changes - don't overthink!
  3. Final Technical Check (10 min):
    • Any bugs found during practice?
    • Quick fixes only
    • Test demo once more

Time: 80 minutes total

Deliverable: Polished presentation ready for assessment

Final Reminders for Presentation Day

Technical:

  • ✓ Laptop fully charged + bring charger
  • ✓ Demo tested on presentation computer
  • ✓ Backup plan ready (screenshots/video)
  • ✓ Slides accessible (USB drive + cloud)

Team:

  • ✓ Everyone knows their speaking parts
  • ✓ Smooth transitions practiced
  • ✓ Timekeeper assigned

Mindset:

  • ✓ You've built something amazing - be proud!
  • ✓ Confidence comes from preparation (which you have!)
  • ✓ You've got this! 🎉

Celebrating Your Achievement

What You've Accomplished:

  • ✓ Worked in a professional agile team
  • ✓ Built a real software system from scratch
  • ✓ Learned industry-standard tools and practices
  • ✓ Collaborated through challenges
  • ✓ Created documentation and presentations
  • ✓ Applied professional and ethical standards

This is Portfolio-Worthy Work!

Add to LinkedIn, GitHub, show to employers.

Taking This Forward

Next Steps:

  • Portfolio: Add project to portfolio site, polish README
  • GitHub: Pin repository, ensure public and well-documented
  • LinkedIn: Post about your project, tag teammates
  • Continue Building: Add those "Won't Have" features!
  • Deploy Permanently: Keep it live to show employers

Skills You Can Highlight:

  • Agile/Scrum methodology
  • Full-stack development (your tech stack)
  • Team collaboration & Git workflows
  • Technical communication

Lecture 12 Summary

  • Presentations assessed on structure, technical explanation, demo, and Q&A
  • Technical implementation judged on functionality, code quality, architecture
  • Documentation and team process are important components
  • Professional standards (security, accessibility, GDPR) matter
  • Practice reduces nerves and builds confidence
  • Constructive feedback helps teams improve
  • You've accomplished something significant!

Good Luck on Your Presentations!

You've prepared well. Trust your work and your team.

Thank You & Good Luck!

To All Teams:

It's been a pleasure watching your projects develop from ideas to working systems.

You've demonstrated:

  • Technical skill
  • Team collaboration
  • Problem-solving ability
  • Professional growth

Well done, and best of luck with presentations!

Questions? Office hours available, or email jwilliams@staff.newman.ac.uk