As someone new to the QA and the testing community, within his organization, Ben was experiencing difficulties testing stemming from communication issues across teams. It felt like he was often the middle-man in a game of telephone between stakeholders, often making it difficult to efficiently manage how they test new features and products. To help address this issue, Ben incorporated mob testing into their testing culture. He will focus on what he has found to be the benefits of mob testing (such as improved communication and relationships among teams & spreading product knowledge), helpful hints for making sure the sessions go well (such as being prepared ahead of times & following up and using temporary Slack channels as a tool), and his journey of how, as a new tester, he helped his organization leverage mob testing to overcome communication difficulties and improve the speed and impact of their testing efforts.
- What does a successful mob testing session look like?
- What are some good and bad things you can do within a session to make it more successful.
- The benefits of mob testing.
- Some small things you can start today to begin mob practices and improve your feature development process.
Ben Oconis – QA Lead, Storyblocks
Ben comes from a customer support background where he has spent 15 years managing customers, dealing with angry people, and helping make their day to day experience better. As a new tester—and the first within his organization, Ben takes that background and previous experience and tries to apply it to find innovative ways to help improve quality across the organization. He has had some great successes and failures and hopes to share those with the testing community.
When not testing, Ben enjoys hanging with his family which includes 2 kiddos, a 5-year-old and 8-month-old, his wife and his old dog Dexter, who is a dachshund mix.