|
| 1 | +# Retrospective: Milestone 5 - Final Presentation |
| 2 | + |
| 3 | +> "Regardless of what we discover, we understand and truly believe that everyone |
| 4 | +> did the best job they could, given what they knew at the time, their skills |
| 5 | +> and abilities, the resources available, and the situation at hand." |
| 6 | +> |
| 7 | +> - [Norm Kerth](http://www.amazon.com/Project-Retrospectives-Handbook-Reviews-Dorset-ebook/dp/B00DY3KQJU/ref=tmm_kin_swatch_0?_encoding=UTF8&sr=&qid=) |
| 8 | +
|
| 9 | +This retrospective is meant for looking back at how Milestone 5: |
| 10 | +Final Presentation Event went and learning what to do differently next time. |
| 11 | + |
| 12 | +## Behaviors, not People |
| 13 | + |
| 14 | +Focus on what your group can _do_ that will make the next sprint better. Keep your |
| 15 | +retrospectives _positive_ and _general_. **_You should NEVER mention people by name!!!_** |
| 16 | + |
| 17 | +## Strategy vs. Board |
| 18 | + |
| 19 | +### What parts of your plan went as expected? |
| 20 | + |
| 21 | +- The structured approach to presentation development, building from our comprehensive |
| 22 | + documentation and dashboard work, allowed us to create a compelling narrative |
| 23 | + that effectively communicated our complete data science journey. |
| 24 | +- The focus on storytelling with data helped us translate technical findings |
| 25 | + (91% correlation, 85% prediction accuracy) into accessible insights that |
| 26 | + resonated with diverse audiences including technical and business stakeholders. |
| 27 | +- The integration of live dashboard demonstrations provided concrete evidence |
| 28 | + of our solution's practical value, making abstract statistical findings |
| 29 | + tangible and actionable for educational institutions. |
| 30 | +- The emphasis on impact metrics (15-25% improvement in completion rates) |
| 31 | + successfully connected our research to real-world educational outcomes |
| 32 | + and institutional value propositions. |
| 33 | + |
| 34 | +### What parts of your plan did not work out? |
| 35 | + |
| 36 | +- Initial attempts to include extensive technical detail proved overwhelming |
| 37 | + for the 2.5-minute format, requiring significant content refinement to |
| 38 | + balance technical rigor with accessibility and time constraints. |
| 39 | +- Coordinating live demonstration timing within the presentation flow required |
| 40 | + more practice than anticipated, as technical demos can be unpredictable |
| 41 | + during high-stakes presentations. |
| 42 | +- Ensuring all team members were equally prepared for potential Q&A sessions |
| 43 | + proved challenging given the breadth of technical and domain expertise |
| 44 | + required to address diverse audience questions. |
| 45 | + |
| 46 | +### Did you need to add things that weren't in your strategy? |
| 47 | + |
| 48 | +- We found it necessary to develop multiple presentation versions (technical |
| 49 | + vs. executive summary) to accommodate different audience segments and |
| 50 | + potential time variations, which wasn't initially planned but proved essential. |
| 51 | +- We incorporated more emphasis on the collaborative process and team learning |
| 52 | + journey, as audiences were particularly interested in the cross-cultural |
| 53 | + collaboration and skill development aspects of the project. |
| 54 | +- We added specific ROI calculations and business case elements to strengthen |
| 55 | + the institutional adoption argument, moving beyond pure research findings |
| 56 | + to practical implementation considerations. |
| 57 | + |
| 58 | +### Or remove extra steps? |
| 59 | + |
| 60 | +- We decided to streamline complex methodology explanations in favor of |
| 61 | + clear outcome communication, focusing on what the findings mean rather |
| 62 | + than detailed technical implementation, to maximize impact within time constraints. |
| 63 | +- We removed extensive background context about online learning challenges |
| 64 | + in favor of immediate problem statement and solution demonstration, |
| 65 | + to maintain audience engagement and maximize solution focus. |
| 66 | + |
| 67 | +## The Four Points |
| 68 | + |
| 69 | +### Stop Doing |
| 70 | + |
| 71 | +- **Over-engineering presentation complexity:** Focus on clear, impactful |
| 72 | + messaging rather than trying to demonstrate every technical capability |
| 73 | + and analytical sophistication within limited presentation time. |
| 74 | +- **Underestimating rehearsal time requirements:** Technical demonstrations |
| 75 | + and timing coordination require extensive practice to ensure smooth |
| 76 | + delivery under presentation pressure. |
| 77 | +- **Assuming audience familiarity with domain context:** Even educated |
| 78 | + audiences benefit from clear problem framing and context setting |
| 79 | + before diving into solution details and technical achievements. |
| 80 | + |
| 81 | +### Continue Doing |
| 82 | + |
| 83 | +- **Narrative-driven presentation structure:** The story arc from problem |
| 84 | + identification through solution deployment effectively engaged audiences |
| 85 | + and made technical work accessible to diverse stakeholder groups. |
| 86 | +- **Live demonstration integration:** Hands-on dashboard interaction provided |
| 87 | + compelling evidence of solution viability and allowed audiences to |
| 88 | + experience the practical value of our research findings directly. |
| 89 | +- **Impact-focused messaging:** Emphasizing measurable outcomes (completion |
| 90 | + rate improvements, early intervention capabilities) successfully connected |
| 91 | + technical work to real-world educational value and institutional benefits. |
| 92 | +- **Professional presentation standards:** High-quality visual design and |
| 93 | + polished delivery enhanced credibility and stakeholder confidence in |
| 94 | + our solution's readiness for institutional adoption. |
| 95 | + |
| 96 | +### Start Doing |
| 97 | + |
| 98 | +- **Multi-format presentation preparation:** Develop presentation materials |
| 99 | + that can be adapted for different time constraints and audience types, |
| 100 | + ensuring flexibility for various presentation opportunities and contexts. |
| 101 | +- **Comprehensive Q&A preparation:** Anticipate diverse audience questions |
| 102 | + across technical, implementation, and business domains to ensure confident |
| 103 | + responses that reinforce solution credibility and team expertise. |
| 104 | +- **Stakeholder follow-up planning:** Prepare materials and processes for |
| 105 | + post-presentation engagement with interested institutions or potential |
| 106 | + collaborators who want to explore implementation opportunities. |
| 107 | + |
| 108 | +### Lessons Learned |
| 109 | + |
| 110 | +- **Presentation is product validation:** The final presentation serves as |
| 111 | + the ultimate test of whether technical work translates into communicable |
| 112 | + value that stakeholders can understand, trust, and act upon. |
| 113 | +- **Storytelling amplifies technical impact:** Even sophisticated analysis |
| 114 | + requires compelling narrative structure to achieve maximum stakeholder |
| 115 | + engagement and adoption likelihood in real-world contexts. |
| 116 | +- **Live demonstrations build confidence:** Interactive elements allow |
| 117 | + audiences to validate findings themselves, creating stronger conviction |
| 118 | + in solution viability than static presentations alone. |
| 119 | +- **Professional presentation multiplies opportunities:** High-quality |
| 120 | + presentation materials and delivery create lasting impressions that |
| 121 | + can lead to future collaboration, employment, and project opportunities. |
| 122 | + |
| 123 | +## Individual Retrospectives |
| 124 | + |
| 125 | +### Fahed |
| 126 | + |
| 127 | +The final presentation milestone taught me that technical excellence means nothing |
| 128 | +without effective communication. Distilling months of collaborative data science |
| 129 | +work into 2.5 minutes forced me to identify what truly matters to stakeholders - |
| 130 | +not the complexity of our methods, but the clarity of our impact. |
| 131 | + |
| 132 | +The experience of presenting live dashboard demonstrations under time pressure |
| 133 | +showed me the importance of preparation and backup planning. Technical demos |
| 134 | +can fail, but the story and insights must remain compelling regardless of |
| 135 | +technical difficulties. This taught me to always have multiple ways to |
| 136 | +communicate the same key message. |
| 137 | + |
| 138 | +Most importantly, I learned that presentations are not just about sharing |
| 139 | +results - they're about inspiring action. Our 91% correlation finding only |
| 140 | +matters if institutions feel confident enough to implement our recommendations. |
| 141 | +The presentation taught me to think like a stakeholder and communicate in |
| 142 | +terms of their priorities and constraints. |
| 143 | + |
| 144 | +### Caesar |
| 145 | + |
| 146 | +The final presentation experience highlighted the critical importance of |
| 147 | +translating technical work into business language and stakeholder value |
| 148 | +propositions. I learned that even the most sophisticated analysis has |
| 149 | +limited impact without clear communication of practical implications. |
| 150 | + |
| 151 | +The process taught me to think beyond technical accuracy toward stakeholder |
| 152 | +adoption and implementation feasibility. Presenting to diverse audiences |
| 153 | +required understanding different perspectives and tailoring technical |
| 154 | +depth to audience expertise and decision-making authority. |
| 155 | + |
| 156 | +Most valuable was learning that presentations are collaborative conversations, |
| 157 | +not one-way information transfer. Engaging with audience questions and |
| 158 | +feedback taught me to defend technical choices while remaining open to |
| 159 | +stakeholder concerns and implementation constraints. |
| 160 | + |
| 161 | +### Team Learning Outcomes |
| 162 | + |
| 163 | +Through Milestone 5, we experienced the complete transformation from technical |
| 164 | +analysis to stakeholder communication, learning that data science projects |
| 165 | +are only successful when findings translate into actionable insights that |
| 166 | +stakeholders can confidently implement. |
| 167 | + |
| 168 | +The collaborative presentation development process taught us that effective |
| 169 | +communication requires the same rigor and iteration as technical analysis. |
| 170 | +Multiple rehearsals, content refinement, and audience consideration proved |
| 171 | +as important as statistical validation and model accuracy. |
| 172 | + |
| 173 | +Most significantly, we learned that presentations are not project endings |
| 174 | +but potential beginnings. High-quality communication of technical work |
| 175 | +creates opportunities for continued collaboration, institutional partnerships, |
| 176 | +and professional development that extend far beyond academic requirements. |
| 177 | + |
| 178 | +The experience prepared us for professional data science roles where |
| 179 | +technical capability must be matched by communication excellence to |
| 180 | +achieve real-world impact and stakeholder adoption. |
| 181 | + |
| 182 | +--- |
0 commit comments