Joel Montvelisky

Co-Founder and Chief Solution Architect, PractiTest.

Joel has been in testing and QA since 1997, working as a tester, QA Manager & Director, as well as a Consultant for companies in Israel, the US and the EU.  Joel is also a blogger with the QA Intelligence Blog and is constantly imparting webinars on a number of testing and Quality Related topics.

Joel is the founder and Chair of the OnlineTestConf, he is also the co-founder of the State of Testing™ survey and report.  His latest project is the Testing 1on1 podcast with Rob Lambert, released earlier this year –

Joel is a conference speaker, presenting in various conferences and forums worldwide, including the Star Conferences, STPCon, JaSST, TestLeadership Conf, CAST, QA&Test and more.

Test Management When Testing is The Whole Team’s Responsibility;

So the mantra goes, in today’s development world that testing is the responsibility of the whole team. But for 90% of organizations (or more), this does not really translate into practice and testing is still mostly the responsibility of the testers. There are many reasons for this but one of the most common is that people who were never testers (in the present or past) do not really know how to test. Even when they want to test, they still need someone to manage the process, guide their testing work and orchestrate the testing process for the project or team. Testing can be everyone’s responsibility, but Test Management still needs to be the responsibility of a Test Architect or Test Specialist.

In this talk, we will review some of the main responsibilities and differences between managing testing in a traditional team versus the work needed on a whole-team-testing-approach.