Our commitment to quality, or How we work with clients to ensure the project's success

In one of our previous posts, we presented you with an overview of our development process and shared our basic working principles. Today we’re gonna dig a little deeper—specifically into the process of partner’s integration into our development ecosystem. Let’s go!

It’s worth noting that we follow the approach of full transparency with our partners and customers. That’s why we work hard to provide all the necessary access for them to make game development productive for everybody.

First of all, we split the ecosystem tools into common and internal ones. The common tools consist of:

• Store console tools (like App Store Connect/Testflight, Google Play Console, Steam, etc.). This is needed to upload test and release builds to be able to test them and provide feedback.
• Customer’s/partner’s source code repository or cloud storage. This is needed to sync and upload source code, so our partners can be safe about having access to the source code and all assets on their side.
• Third-party cloud services (like AWS, Digital Ocean, Firebase, Adjust, Applovin MAX, etc.). We may integrate some third-party services, and it’s essential that both sides have access to them since our partners/customers might like to see analytics, billing, etc.

As for the internal tools, we have the following main categories of software tools:

• Task Management tools where we create tasks, control the estimations, task statuses, etc. As for examples, we use widely Atlassian Software products (Jira and Trello in this particular case), also Monday, Asana, and OpenProject.
• Documentation tools, where we store all our documentation regarding projects and corporate processes. Confluence and BookStack served these purposes quite well.
• Source Code Repository tools. Here we store all the source code during the development (GitHub, GitLab, Bitbucket)
• Design tools where we create source files of the design layouts (Figma)
• Messaging tools, where we communicate inside our team. We use Slack for that purpose.

We outlined the two main groups of software that we use in our daily processes, but it's worth highlighting that our partner can be integrated into any of the internal tools depending on the responsibilities of the needed person.

Here are some examples:

— A product owner would definitely need access to the task management tool to understand the status of the development, but they also need access to the documentation and design tool to view/update the documents, and provide feedback.

— Partner’s QA team would need to provide test reports and bugs, so, they also need access to the task management tool and the documentation, so, they can have all the needed information to compare the expected result with the real result.

— If our customer or a partner has their own developers/designers or other team members, we will add them to the needed tools accordingly.

— As for the communication, we are flexible here as well. We can easily add the partner’s team members to our Slack channels, or we can be easily integrated into any partner’s/customer’s communication software that is needed.

We understand that not everybody is familiar with the software we use as there are many tools for productivity nowadays. We gladly provide the onboarding process with some important documentation and personal calls — everything to make our partners familiar with the software we use.

We work hard to improve our competencies and to make the development and communication processes easier and even more transparent. We can ensure that working with us is not only about making a profit but about pleasure as well. As we ourselves enjoy what we do and transfer this joy to the outer world.