Get ready to dive into Miro’s transformative journey as they redefined quality assurance by decentralizing the QA process. Join Anton Necheukhin, Head of QA at Miro, as he shares how Miro empowered teams to take ownership of quality and successfully navigate the shift toward QA decentralization.
Still not registered? Hurry up and grab your free tickets: Register Now!
Already registered? Drop your questions in the thread below 
Hi there,
If you couldn’t catch the session live, don’t worry! You can watch the recording here:
Here are some of the Q&As from this session:
how do you manage the feature flags ?
Anton Necheukhin: Feature flags are managed by integrating them into the development and testing workflows. This involves using tools to toggle features on and off in different environments, allowing for targeted testing and gradual rollouts. Consistent documentation and clear communication across teams are essential to avoid confusion and ensure that everyone is aware of the current state of each feature.
What do you see as the next evolution in testing?
Anton Necheukhin: The next evolution in testing is likely to involve even greater automation, leveraging AI and machine learning to create smarter, more adaptive testing processes. This could lead to predictive testing, where potential issues are identified and addressed before they even occur, based on patterns and data analysis.
How big of a company is this assignment matrix ideal for? Listening from a startup, a lot of this shifts as expected with a smaller team.
Anton Necheukhin: The assignment matrix is generally more suited to medium to large companies, where there is a clear need to coordinate tasks and responsibilities across multiple teams or departments. For startups with smaller teams, the structure tends to be more fluid, and roles can shift quickly, so a more flexible approach is often necessary.
Here are some unanswered questions that were asked during the session:-
How do you ensure that these processes are effectively implemented and followed by your teams?
The description sounded like this was planning to remove the role of QA?
Or change the role of QA - give devs more white box testing while focusing QA with high domain knowledge on integration, performance and UX testing. Is that correct? And does UX testing include beta testing?
For ETL testing how it use it. is there any plugin required ?
the description sounded like this was planning to remove the role of QA?
How do you manage the feature flags ?
Have you any tips for getting teams to take ownership of there technical products? I’m based in a very wide spread organization and it always seems to be a challenge to get teams to make there dependency stable in test environments
How big of a company is this assignment matrix ideal for? Listening from a startup, a lot of this shifts as expected with a smaller team.
Anton Necheukhin: The assignment matrix is generally more suited to medium to large companies, where there is a clear need to coordinate tasks and responsibilities across multiple teams or departments. For startups with smaller teams, the structure tends to be more fluid, and roles can shift quickly, so a more flexible approach is often necessary.
Where should QA reside in an R&D hierarchy?
How are the rituals that the QA community follow?
How much human oversight or leadership is required to manage autonomous Q/A teams, especially those leveraging AI and automaton tools?
How many sdet’s do you have in house?
Will there be a pivot back to human-led testing, or will here more be use of AI and automation over, say, the next year?
“Can we use pytest in the session ‘Empowering Teams for Autonomous Quality Excellence’?”
Thank You Anton for the Session, Here is the Answer
Anton made it clear that the goal was not to eliminate the QA role but rather to redefine it. The shift toward decentralization meant that developers were encouraged to take on more testing responsibilities, especially when it comes to unit and integration testing. QA professionals, on the other hand, moved toward more specialized areas such as performance, security, and usability testing. The role evolved to focus on ensuring the quality of the testing process itself and driving quality culture across teams, rather than performing all tests themselves.
