Collaborate and Lead: A Scrum Story from the Dev Trenches
Michael Khripin
Writer, LiveOps Expert at Balancy, Co-Founder at New Perk Ltd, Owner of "Game Dev Uncovered" blog
In the ever-evolving world of game development, ‘collaborate and lead’ isn’t just a fancy mantra; it’s the bread and butter of making things happen. Let me take you back to a time at a company I worked with, where we put a little twist on the Scrum methodology.
Picture this: independent, fully-functional Scrum units, each a mini-ecosystem of game designers, QA experts, client and backend developers, and artists. By the book, these units should run the gamut – stand-ups, sprint demos, retrospectives, you name it. But here’s where we threw the book out of the window (metaphorically, of course). We didn’t have a dedicated scrum master orchestrating this symphony. Instead, we decided to pass the baton around, letting each team member lead aspects of the process.
The results? Some discovered they had a knack for jazzing up stand-ups, while others turned out to be maestros of retrospectives. This approach wasn’t just about keeping the team lean or saving a penny here and there. It was about giving everyone a chance to dip their toes into leadership waters, to stretch their skill set beyond their comfort zones.
Sure, for the introverts among us, this felt less like an opportunity and more like a punishment. But even they found their groove, or at least learned a thing or two about swimming against the current.
So, here’s a toast to collaboration and leadership, to stepping up and out, and to the occasional discomfort that pushes us to grow.
Have ever been in comfort zone?
Raise your cup,
PixelWraith
Subscribe to "Game Dev Uncovered" channel!