The world of software testing has made many important advances in techniques and approaches, but is it keeping up with the leaps and bounds of technology's progress? Mike Sowers is an advocate for a revolutionary breakthrough in software testing, and to get there, we all need to become innovators. Here's how.
Mike Sowers has more than twenty-five years of practical experience as a global quality and test leader of internationally distributed test teams across multiple industries. Mike is a Training Line of Business Leader and a Senior Consultant, skilled in working with both large and small organizations to improve their software development, testing, and delivery approaches. He has worked with companies—including Fidelity Investments, PepsiCo, FedEx, Southwest Airlines, Wells Fargo, ADP, and Lockheed—to improve software quality, reduce time to market, and decrease costs. With his passion for helping teams deliver software faster, better, and cheaper, Mike has mentored and coached senior software leaders, small teams, and direct contributors worldwide.
All Stories by Michael Sowers
When it comes to the development, testing, and deployment of software, some argue that metrics have little value. Others take measurement to the extreme and have books of metrics, but without any meaning or action. Mike Sowers thinks metrics are vital, but it’s most beneficial to have just enough metrics.
If our goal as testers is to build and release code more rapidly, frequently, and reliably, we must also align and integrate our testing practices, testing tools, test cases, test data, and test environments into continuous integration, testing, and deployment. A DevOps culture yields all new opportunities.
A tester starting in the profession recently asked Michael Sowers, "What are some of the most common mistakes we make as testers?" He wrote down some of the more common ones he could think of that are made before, during, and after testing. How many of these could you turn into learning opportunities?
These days, data comes from multiple sources, is transformed in many different ways, and is consumed by hundreds of other systems, so we must validate more data, more quickly. Mike Sowers shares his work in progress checklist for things to consider when developing a test strategy and design approach for data.
As our world becomes more complex, the demand for technical testing expertise is going up. While there will always be a need for domain specialists, we also need just as many technical testing roles—particularly with programming skills. Mike Sowers has some ideas on developing additional technical expertise.
Many companies are striving to test earlier. But goals and principles are always easier to articulate than they are to implement. Often, this is less of a technical issue and much more an organizational, change management challenge. Michael Sowers talks about the steps to take to make things happen.