Are you tired of working on user stories that seem to be missing vital details for testing? Are you frustrated with being left out of vital design conversations? Or are you fed up with sizing estimates that never turn out to be true to reality? Then it’s time to stop guessing your way through product development and start planning it with better behavior discovery. In this tutorial, we will learn how three vital roles – business, development, testing – can collaborate on what features to build and test through the structured activities of story mapping and example mapping. We will practice...
Andrew Knight
Senior Director of Product Management
Cycle Labs
Andrew Knight, also known as “Pandy,” is the Automation Panda. He’s a software quality champion who loves to help people build better quality software. Currently, he works as the Senior Director of Product Management at Cycle Labs, focusing on building an excellent test automation platform for enterprise systems. Previously, Pandy spent a decade as a SDET building solutions to testing problems at various tech companies. He also previously led Developer Relations and Test Automation University at Applitools. As an avid supporter of open source software, Pandy is a Playwright Ambassador as well as the lead developer for Boa Constrictor, the .NET Screenplay Pattern. On the side, he is writing a book on software testing with Manning Publications. Apart from software, Pandy spends time with his family, his French Bulldog, and his vintage Volkswagens. Check out his tech blog at AutomationPanda.com, and follow him on Twitter at @AutomationPanda.