Over the past few weeks in CM-348, we’ve been learning about Scrum and how it’s used in team-based environments. Before this class, I had heard the word tossed around in tech spaces and job descriptions, but I didn’t fully understand what it meant. Now that we’ve gone through some of its core ideas in class, it’s starting to make more sense. Scrum is a framework that helps teams stay organized, break up big projects into smaller pieces, and work together efficiently, even when plans or priorities change.
To learn more outside of class, I watched a video on YouTube titled “Scrum in Under 10 Minutes” by The Agile Coach. It’s a short breakdown of how Scrum works, why it’s useful, and the key roles and events involved, like the Product Owner, Scrum Master, sprint planning, daily stand-ups, and retrospectives. It gave me a clearer picture of how teams actually use Scrum in real-life software projects and how those short sprint cycles keep things moving forward without getting stuck in too much planning.
I picked this video because it connects directly to what we’ve been doing in CM-348 and helped me visualize how everything fits together. The video was quick but packed with helpful context, and it explained the same terms we’ve been using in class. I wanted to find something that would reinforce what we’re learning while also giving me a glimpse of how this works in practice outside of school.
What I liked most about the resource and about Scrum in general is the focus on communication and reflection. It’s more than checking off tasks, it’s about talking with your team regularly, making adjustments, and working in cycles. That really connects with our work using Git and GitHub. Every commit tells a story of progress, and every pull request is a small review. Scrum brings that same kind of accountability and structure to the whole project process.
Watching this video helped me see how important soft skills are in tech roles. Communication, time management, and teamwork are just as important as technical skills. It also reminded me that being flexible is key; you have to be ready to pivot and adapt when things don’t go as planned. As I move closer to graduating and start looking at jobs, I want to take what I’ve learned about Scrum and apply it in myroles. Even personal projects could benefit from this kind of organization. I could plan out sprints, reflect on progress, and stay focused on what matters.
Scrum is helping me connect the dots between managing code and managing people and tasks. Between that and what we’re doing in Git, CM-348 is giving me tools to work better and smarter, both on my own and in teams.
From the blog CS@Worcester – Tristan CS by Tristan Coomey and used with permission of the author. All other rights reserved by the author.