Sprint 2 Retrospective #6
Description
Retrospective – Sprint Reflection & Personal Focus Goals
🏗️ Previous Sprint Summary
In the last sprint, I took on the role of a Learning Experience Designer with my team.
Our project was an M&M game where players:
- Walked up to different M&Ms and gained steps on how to change the theme using a Makefile.
- Encountered little quizzes tied to key concepts.
- Explored two different game levels designed for engagement and progression.
This project was both a creative coding exercise and an opportunity to think about how students learn best through interactivity.
✅ What Went Well
- Team Collaboration: Strong teamwork in building out game mechanics and tying them to learning outcomes.
- Creativity: Using M&Ms as interactive elements made the learning process fun and unique.
- Learning Design: Incorporated quizzes + levels to reinforce knowledge and provide challenge.
- Technical Growth: Gained more comfort with Makefile usage and integrating it into a game environment.
- Engagement: The project was memorable and interactive, something that peers enjoyed trying out.
⚠️ Challenges
- Time Management: Balancing design creativity with technical implementation.
- Clarity of Instructions: Some steps in the game/quiz flow could have been explained better to players.
- Polish: The game mechanics worked, but some parts felt rough or rushed.
- Feedback Cycle: We could have used peer/teacher feedback earlier in the process to refine design decisions.
🎯 Personal Focus Goals for Next Sprint
Based on my own reflection and feedback from peers, here are my focus goals:
1. Lesson & Game Design
- Prioritize clearer instructions so players/learners always know what to do next.
- Ensure activities (quizzes, levels, hacks) directly tie back to Big Idea 1 & 3 learning objectives.
- Build projects that balance fun + educational value.
2. Technical Growth
- Strengthen JavaScript visualization skills for the Sprint 2 Final Hack.
- Explore Flask + Python integration for creative projects.
- Push for cleaner, more polished code (especially with Makefile and build tools).
3. Collaboration & Feedback
- Actively seek peer feedback earlier in the design cycle.
- Take stronger role in issue tracking and planning to keep work on schedule.
- Share my learning progress on the blog more consistently for transparency.
4. Beyond Perfunctory
- Add more personal creativity into projects so they stand out as mine.
- Document my contributions so they are visible in GitHub Issues & PRs.
- Build projects that are not only functional but also memorable and polished.
🔄 Next Steps
- Carry lessons from the M&M Game project into Sprint 2 by designing activities that are interactive, clear, and tied to learning objectives.
- Keep blog updated with reflections and progress to show growth from Sprint 1 → Sprint 2.
- Use peer and teacher evaluations more deliberately to refine my work.