My QA Principles

In terms of running a QA Department through a project's life cycle, I believe there needs to be a good balance between QA being flexible to change on the project and knowing when to compromise and setting it's own priorities. 

Data is QA's bread and butter and I think it's important for a QA Department to collect, maintain, analyze and utilize Data to not just drive it's own initiatives and priorities but inform and make available data for others so that they may do the same.

QA Departments are one of the few departments in the development pipeline that need to interact with almost every other department. This requires good processes, understanding of different dependencies and the use of proven models such as RACI & Skill Matrices.

Creating games is a highly collaborative process and it's important to rally everyone involved behind a common goal at every step of the way.

With so many stakeholders and dependencies within a game development process communication and the breaking of silos is essential. Communication is also an essential skill for QA to master as it isn't always easy to point out flaws in the work of others.

Primarily detailed within the "Management Principles" section, I believe in the power and importance of being first and foremost a good People manager that leads with empathy, knows how to support and upskill People and when to have difficult conversations.