Ladutko Andrey
Head of QA / QA Architect - PandaDoc
Minsk, Belarus

Head of QA Department in product company

  • 12 years in testing
  • 5 years in test management
  • 3 years in trainings conduction
  • presenter since 2012, program committee member since 2014
  • more than 15 QA Assessments with different teams and goals
  • ISTQB Full Advanced Level specialist (Test Analyst, Test Manager, Technical Test Analyst)

My favourite topics are test strategies, test design, people management

Talks (10)
  • 26.07.2021
    QA Career - is growth possible behind the Senior level, but not in Management track

    Congrats, you have achieved the Senior QA level on the project! What's next? Probably, it is not expected from you to grow - 100% expectations from you on the project are met. Should you stay senior, or move to engineering management, or continue to sharpen your tech skills? But is it enough tech skills only on the Senior+ level?

    In my talk, I'll tell how I answered these questions and share practical advice on how to grow as QA in the direction known as "Individual Contributor" in such companies as Microsoft, Uber, Stripe, and Amazon. And the roles called here - are Staff and Principal Engineer.

    • Average
    • 40 min
    • SQA Days / 29
  • 14.03.2019
    OKR and QA - practical advices

    OKR (Objectives and Key Results) is a goal system used by Google and others. It is a simple tool to create alignment and engagement around measurable goals.

    What happens with quality when a company moves to the OKR objectives setting system? How can OKR goals affect product quality positively or negatively? What should be done so that the quality does not "sink" in the transition period and in general when implementing OKR? How is OKR related to the development of the team - CFR - and how does the work with the team change during the transition? 

    I will answer all these questions in the talk and share the practical experience.

    • Average
    • 1 h 30 min
    • SQA Days / 25
  • 24.02.2019
    Economics of software testing, v.2.0

    The continuation of Alexander Alexandrov's talk "Economics of software testing, v.2.0" where we will extend the field for discussions and discuss the issues of the economics of testing with the audience.

    The main points of the talk: 

    • Exhaustive testing is not possible. 
    • Testing is as well an economic activity. 
    • Version 1.0, or What need to do. We work within a plan and evaluation, when a lack of resources, we ask to add them (extensive approach).
    • Version 2.0, or How need to do. We work within a plan and assessment as efficiently as possible (intensive approach).

    The round table will be devoted to the discussion on how to proceed to version 2.0, analysing the following tasks and using reasonable labour costs efficiently, analysing: 

    • What the test cases we need (do we really need them?). 
    • What the test data we need.
    • What testers we need - a few strong ones (but expensive) or many of weak (but inexpensive). 
    • What kind of automation we need (do we need it at all), what tools, coverage.

    • Hard
    • SQA Days / 25
  • 23.07.2018
    The Expert test manager - Why You Cannot Become One and What Follows from This

    What is the talk about? 

    Which tester does not dream of becoming a leader, preferably ideal? I have two news for you: good and bad. A good one - to become a test-manager really, and there are various options for developing you as a test manager. A bad one - to be an ideal is impossible, but as Adizes says about the manager, "you can polish the edges of your personal effectiveness and be effective in one, maximum - in two areas." 

    Why should you come to the talk? 

    • A look at the test management from various perspectives: Rex Black's book "The expert test manager", Adizes "The Ideal Executive", Henry Neave "The Deming dimension," and others. 
    • My personal experience and not just a "retelling" of books (albeit very valuable ones). 
    • Plan what to do next in your growth as the test manager
    For whom is this talk? 
    The talk is addressed to test-leaders, test-managers, and testers who want to see a little more than a step forward.

    • Average
    • 40 min
    • SQA Days / 24
  • 17.09.2017
    TEST-manager or test-MANAGER - solving incoming tasks

    На этом круглом столе, как и на предыдущем, предлагается обсудить озвученную проблему и всколыхнуть аудиторию, получить ответы / соображения / высказывания / мнения по ситуациям/проблемам, которые мы предлагаем для обсуждения:

    - Выполнять тестирование проекта с учетом специфики доменной области

    - Обучить команду навыкам поиска, занесения и управления дефектами (defect management process)

    - Обучить команду тест-дизайну

    - Разработать тестовую стратегию основного продукта и независимых стримов продукта

    - Провести оценку трудозатрат на тестирование

    - Построить план-график работ по тестированию, распределять обязанности (включая бекапирование ключевых ресурсов)

    - Мониторить выполнение работ по тестированию

    - Готовить отчеты по активностям тестирования и качеству продукта 

    - Нанимать и обучать тестировщиков (в том числе и при дефиците ресурсов)

    - Разрешать сложные ситуации(некачественный тест-дизайн, отклоненные дефекты, конфликты с другими экспертизами)

    • Average
    • SQA Days / 22
  • 10.01.2017
    Round table discussion: TEST-manager or test-MANAGER?

    There were many replies from listeners during the talk of Aleksandr Aleksandrov "Current State vs. Common sence" on SQA Days-20 in Minsk, like "Everything you talk is test manager's business", and there were a long after-speech discussion in lobby.

    We have found out, that role of test managers is understood differently by all listeners.

    During this round table, we are going to discuss mentioned problem and arise auditory, to get answers / thoughts / ideas / opinions for topics we propose to discuss.

    - Could you learn to become test manager (and testing)?
    - What would (and wouldn't) test manager do on the project?

    - Can we work without test manager (and test management)?

    - What would you do if project manager rules everything, and testers are not always agree with him?

    - Does manager ought to "move away" from testing, and if ought to, how to understand, how much?

    - Does manager ought to be "a barrier" for direct communication between testers and "outside world, and how much?

    • Average
    • SQA Days / 21
  • 27.04.2016
    Self QA process assessment: how to start?

    Test process assessment could be both: in-depth, with calling external experts and self-assessment. In my talk, I'll describe self-test assessment process, how to start, hot to set goal, assess, select improvement and track the progress.

    • Average
    • 20 min
    • SQA Days / 19
  • 29.03.2015
    How to assess testing process on the project

    Testing is constantly changing process requires in continuous improvements. We identify them on retrospectives, from our and other's experience and mistakes, based on intuition or analyzed data.

    In my talk, I'll tell you, how to assess testing process on the project: how to start, where to pay attention. I'll share practical experience and answer on your questions. See you on the talk!

    • Average
    • 40 min
    • SQA Days / 17
  • 29.08.2014
    White box adventures in the land of coverage

    Each of us knows (or at least heard) about boxes, their kinds and testing techniques for each of them. I'll tell about "the light side" - white-box testing techniques.

    BTW, it's will be a master-class, so you leave your textbooks and come to solve practical tasks and looking for real examples. Happy to see you on master-class!

    • Easy
    • 40 min
    • SQA Days / 16
  • 28.01.2014
    Time Management in Quality Assurance

    Ask 100 testers to describe their job and you’ll get 100 different answers. Lucas Dargis We are working in different ways, productively and not very, each of us has own area of responsibility, we even test today not the same way as yesterday. And this is our strength - we find different bugs, form the comprehensive overview of tested system - and make the software world slightly better. But each of us has only 24 hours per day, but we want to catch a lot. In my report I will talk about the organization of time, how to do more testing, how you can build your system in your organization time quality control process. 40 minutes - no more. Less theory - more practice. See you on the report!

    • Average
    • 40 min
    • SQA Days / 15
To leave a feedback you need to

Chat with us, we are online!