SCDS Course Materials

Module 14: Project Presentations and Reflections

Introduction

The final module of DATA 201 brings together everything you’ve learned through the lens of your projects. You will present your work to your peers, receive and give feedback, and reflect on your journey through data science.

Presenting technical work is itself a critical skill. The ability to explain complex analysis to diverse audiences—technical experts, domain specialists, and general audiences—determines whether your work has impact beyond your own understanding.

Part 1: The Art of the Data Science Presentation

Structure of an Effective Presentation

A strong data science presentation follows a narrative arc:

1. The Hook (1-2 minutes)

2. The Question (1 minute)

3. The Data (2-3 minutes)

4. The Approach (3-5 minutes)

5. The Findings (5-7 minutes)

6. The Implications (2-3 minutes)

7. Conclusion (1 minute)

Visualization for Presentation

Slides are not documents. Apply different principles:

Less is more: One idea per slide. Large fonts. Minimal text.

Visualization-centric: Show, don’t tell. Let the data speak.

Annotation: Highlight the key point on each chart. Don’t make the audience find it.

Simplification: Charts for papers ≠ charts for presentations. Simplify for the screen.

Color and contrast: Visible from the back of the room. Consider colorblind viewers.

Handling Questions

Questions are opportunities, not attacks:

Listen fully: Don’t prepare your answer while they’re still talking.

Clarify if needed: “Just to make sure I understand—you’re asking about X?”

Be honest: “I don’t know” or “We didn’t investigate that” are acceptable answers.

Stay focused: Don’t let one question derail into a long tangent.

Bridge to your findings: Connect questions back to your main points.

Common Presentation Mistakes

Too much content: Trying to show everything you did. Focus on what matters.

Too technical too fast: Losing the audience in jargon and methods.

Burying the lead: Saving the interesting findings for the end. Lead with insights.

Reading slides: If you’re reading, the audience is reading faster and not listening.

No story: A presentation is a narrative, not a documentation of steps.

Ignoring time: Rushing through the end because the beginning took too long.

Part 2: Giving and Receiving Feedback

The Art of Constructive Feedback

When giving feedback on peers’ presentations:

Be specific: “The second visualization was confusing because the legend was too small” is more helpful than “I didn’t understand some parts.”

Be constructive: Offer suggestions, not just criticism.

Acknowledge strengths: Note what worked well, not just what could improve.

Focus on the work, not the person: “The analysis could be stronger” not “You didn’t do enough analysis.”

Ask genuine questions: Questions that help clarify understanding or push thinking further.

Feedback Framework: WWW/EBI

What Went Well (WWW):

Even Better If (EBI):

Receiving Feedback

Feedback is a gift—even when it stings:

Listen without defending: The impulse to explain or justify is natural but counterproductive during feedback.

Ask clarifying questions: “Can you say more about what was confusing?”

Take notes: Don’t rely on memory.

Thank the giver: They’re investing time to help you improve.

Separate signal from noise: Not all feedback is equally useful. Consider, then decide.

Part 3: Reflection on Learning

The Reflective Data Scientist

Technical skills are necessary but not sufficient. The ability to reflect—on process, on decisions, on growth—distinguishes a mature practitioner from a novice.

Questions for Self-Reflection

On Your Project:

On the Course:

On Your Future:

The Portfolio Mindset

This project becomes part of your portfolio—a demonstration of your capabilities:

Document thoroughly: Future you (or future employers) will appreciate clear documentation.

Publish if appropriate: GitHub, personal website, blog post.

Iterate post-course: Projects can be extended and improved after the course ends.

Part 4: What Comes Next

Continuing the Journey

DATA 201 is a beginning, not an end. Paths forward include:

Deepen Technical Skills:

Expand Domain Knowledge:

Build Community:

Stay Current:

The Ongoing Responsibility

As you develop capabilities in data science, you assume responsibilities:

Technical Rigor: Don’t fool yourself. Be honest about uncertainty and limitations.

Ethical Practice: Consider impacts. Ask who benefits and who might be harmed.

Communication: Make your work accessible. Science hidden is science lost.

Mentorship: As you learn, help others learn.

Presentation Schedule Format

Session Structure (3 hours)

Introduction (10 minutes)

Presentations (2 hours)

Feedback Session (30 minutes)

Closing Reflection (20 minutes)

Presentation Rubric

Criterion Excellent (9-10) Good (7-8) Adequate (5-6) Needs Work (<5)
Opening Hook Compelling, memorable, establishes importance Engaging, clear context Basic intro, somewhat engaging Weak or missing
Clarity of Question Crystal clear, well-motivated Clear and understandable Somewhat clear Unclear or missing
Data Explanation Excellent intuition building, honest about limits Good explanation, most limits noted Adequate, some gaps Confusing or incomplete
Methods Explanation Accessible, intuitive, well-justified Clear, justified Understandable with some gaps Too technical or unclear
Findings Presentation Insight-led, well-visualized, compelling Good visualizations, clear points Adequate, some issues Unclear or poorly presented
Interpretation Thoughtful implications, honest limits Good interpretation, some limits Basic interpretation Weak or missing
Visual Design Professional, clear, effective Good design, mostly effective Adequate, some issues Poor or distracting
Delivery Confident, engaging, good timing Good delivery, mostly good timing Adequate, some timing issues Poor delivery or timing
Q&A Handling Thoughtful, honest, connects to work Good responses Adequate responses Struggled with questions
Overall Impact Memorable, would recommend to others Interesting and informative Adequately conveyed the project Failed to convey project value

Final Reflection Assignment

Due after presentations, submit a 2-3 page reflection addressing:

  1. Project Reflection
    • What was the core insight from your project?
    • What was your biggest challenge and how did you address it?
    • What would you do differently if you had more time?
  2. Presentation Reflection
    • What worked well in your presentation?
    • What feedback did you receive and how would you incorporate it?
    • What did you learn from other presentations?
  3. Course Reflection
    • What was your most significant learning in DATA 201?
    • How has your understanding of data science evolved?
    • What ethical considerations will guide your future work?
  4. Looking Forward
    • What topics do you want to explore further?
    • How do you see data science in your future career or life?
    • What’s your next step in learning?

Closing Thoughts: From Data to Wisdom

You began this course learning to manipulate arrays and DataFrames. You end it having told a story with data—a story that required not just technical skill but judgment, creativity, and integrity.

Data science at its best is not about algorithms or code. It’s about understanding the world, asking good questions, and communicating insights that matter. The tools will change. The libraries will be updated. The techniques will evolve. But the fundamental challenge—transforming data into wisdom—remains eternal.

You now have the foundation. The rest is practice, curiosity, and care.

Welcome to the community of data scientists.

Module 14 brings DATA 201 to a close with project presentations, peer feedback, and reflection on the learning journey. The ability to present technical work effectively and to reflect honestly on one’s practice are as important as any algorithm we’ve learned.