Hi, I’m Vojtěch Barta

My path spans hands-on exploratory testing, test leadership, mentoring, and training. I’ve built and led QA teams — always balancing human and automated approaches, keeping strategy shifted left to avoid later surprises.

• Vivicta — Test Manager: leading a test team of 10+ members, balancing hands-on testing with strategy and defect prevention, with deep business understanding and requirements analysis.
• Vendavo — QA Lead for Vendavo PricePoint: test strategy, whole-team quality, automation aligned with the test pyramid, measurable improvements in quality and customer outcomes. Long-term product stabilization and modernization.
• Czechitas — Senior lecturer: intensive 3-month courses preparing women for junior testing roles, with a focus on human-centric testing beyond automation.
• TechMeetup Ostrava — Full responsibility for the QA Stage at a 500+ person conference.
• Earlier roles include QA Lead, Test Manager, Tester, and Scrum Master.

Quality is stakeholder satisfaction. “Quality” isn’t a QA gate at the end—it’s whether customers, users, and the business get value without unacceptable risk. That means the whole delivery team aligns on outcomes, risks, and what “good enough” means in context.

Testing is essential—but it’s not the whole story. Assurance covers prevention, collaboration, feedback loops, and learning from production—not only executing test cases. I care about clarity of requirements, testability of design, and catching the right problems at the right time.

Balance structure and exploration. Scripted checks and charters both have a place. Exploratory testing brings learning and adaptation; structured coverage helps where repeatability matters. Together they reduce unnecessary risk without slowing discovery.

Automation where it earns its keep. Effective automation supports fast feedback and frees people for work only humans do well—especially when it respects the test pyramid and avoids brittle, low-value suites.

Defect prevention beats late bug hunting. Reviews, pairing, refinements, CI, and a culture where quality is owned by the team—not “thrown over the wall” to testers—are how I prefer to invest time.

Agile approaches and fast feedback. I’m a strong believer in iterative delivery—whether Scrum, Kanban, or a pragmatic hybrid—and in short feedback loops so teams surface risks early and adjust before problems compound. Transparency, inspection, and adaptation apply to quality as much as to scope and dates. I’ve put that into practice as QA Lead, Scrum Master, and coach.