STARWEST 2019 - Leadership
Wednesday, October 2
The Who, What, Where, When, and How of Test Strategies
What is a test strategy, and how do you develop one? Join Janna Loeffler as she talks through developing a test strategy. She’ll discuss how different software development methodologies influence your test strategy, as well as how techniques like common and coordinated test planning and risk-based testing can be applied to the creation of your test strategy to improve its quality. Janna will also detail how to develop a test strategy when working with different team dynamics; for example, does your test strategy look different for internal teams versus developing a test strategy when...
Thursday, October 3
Are You the Best Leader You Can Be?
We are all leaders. At a minimum, we must lead ourselves every single day, but many of us also have teams that we lead and serve. Have you ever stopped to analyze yourself to determine if you are the best leader you can be? Amy Jo Esser has had the joy of learning from many great leaders outside the testing arena, including John C. Maxwell, Tony Robbins, Mel Robbins, Brendon Burchard, Michael and Megan Hyatt, and Rachel Hollis. She continues to learn from leaders in our testing community, including the inspiring leaders and speakers who have been a part of the Women Who Test community....
Driving Quality with the "Yes, If ..." Mentality
It can be easy to feel like the villain when you work in testing and QA. After all, part of the job is to point out when things are broken, people have made mistakes, timelines aren't realistic, or a plan just can't work. But if your team feels like you're a frequent naysayer, trust can and will erode, and quality suffers because of it. If you find yourself constantly saying, "No, because ..." and being the baddie, it's time to reframe how you approach your team's ideas and development processes. Join Jane Jeffers as she talks about the power of instead saying, "Yes, if ..." and what this...
Scaling Quality through Community Leadership
PreviewModern software development organizations often build teams around features. Unfortunately, these teams tend to become siloed, building tools and processes without being aware of how other teams have solved the same problems. As quality and test engineers are federated out to these feature teams, quality itself becomes decentralized. And as an organization scales, this fragmentation can put product health at risk. How does an organization provide guidance and standards to decentralized teams? How can information, tools, and resources be shared among quality engineers? Can we bring...