Working using the Agile principles

At eXplore Studio, we see the value of taking an agile approach to our work. This working style still includes two structured weekly meetings with the whole team, with a scrum planning meeting on Monday and a technical meeting on Thursday. Nonetheless, throughout the week we are flexible and maintain strong lines of communication. This means we are continuously in touch to share our insights and prioritise our working connections as a team. Equally, the agile approach gives clear advantages when developing working products which we continuously refine. Through this technique, we avoid striving for perfection from the outset and learn that we can evolve as we go. Testing and asking for feedback are also a huge part of this process, as we then do not end up with a “finished” product which needs to be wholly altered. Concentrating on progress over perfection means we can keep work going, instead of going into the pitfall of endless minor revisions. Moreover, we are open to change and expressing different opinions as we know the benefits of diversity of thought. Creativity breeds from experimentation and being able to respectfully disagree, to find solutions and innovate. Therefore, we focus on creating safe spaces at work to discuss various options and ways of carrying out projects.

As a Studio, we remind ourselves of the importance of saying “no” when necessary. How such a little word can build so much guilt and shame in many work cultures is something we wish to manifestly avoid. We believe in recognising our limits and respecting the reality that we can only accomplish so much within the time constraints of a day. Having a proper work-life balance is not always simple but absolutely necessary. Many game developers have separate jobs or other responsibilities alongside game development, so to prevent burn out is key. Continuously saying “yes” may seem kind to the people asking you to carry out a task but can also be a sure fire way to destroy sustainable development. It can lead to overcommitting and undermining long-term productivity. Instead, one needs to see the bigger picture and weigh whether said task is helpful. To say “no” effectively, you can suggest an alternative method which is less time consuming, ask if work can be spread out, or given to someone with a more suitable skillset. By realising that saying "yes" to one task often means saying "no" to others, we take a thoughtful and balanced approach to managing our workload.

Ultimately, being able to respectfully decline certain projects or tasks is not about avoiding work. The opposite is true - it is about prioritising work which suits one’s unique strengths and prevents too much pressure growing for one person. This is a crucial aspect of maintaining a healthy, sustainable work culture where we are focusing our energy and expertise on the work that truly matters. This approach supports both personal well-being and the long-term success of our projects.

Disclaimer: This DevLog is intended to help anyone, who is in a similar situation we are in at the moment. Everyone has to make their own decisions. This merely is our own honest view and opinion, based on our experience. We would love to hear from you, what you think about it all. We wish you all the success and fun you deserve with the development and release of your game! eXplore Studio