To be most effective, test managers must develop and use metrics to help direct the testing effort and make informed recommendations about the software’s release readiness and associated risks. Because one important testing activity is to “measure” the quality of the software, test managers must measure the results of both the development and testing processes. Collecting, analyzing, and using metrics are complicated because many developers and testers are concerned that the metrics will be used against them. Join Mike Sowers as he addresses common metrics—measures of product quality, defect removal efficiency, defect density, defect arrival rate, and testing status. Learn the guidelines for developing a test measurement program, rules of thumb for collecting data, and ways to avoid “metrics dysfunction.” Mike identifies several metrics paradigms and discusses the pros and cons of each.
Michael Sowers
Michael Sowers, CIO and senior consultant at TechWell, 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 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.
In test automation, we must often use several tools that have been developed or acquired over time with little to no consideration of an overall plan, architecture, or the need for integration. As a result, productivity suffers and frustrations increase. Join Mike Sowers as he shares experiences from multiple organizations in creating an integrated test automation plan and developing a test automation architecture. Mike discusses both the good (engaging the technical architecture team) and bad (too much isolation between test automators and test designers) on his test automation journey in large and small enterprises. Discover approaches to ensure that the test tools you currently have and the new test tools you acquire or develop will work well with other testing and application lifecycle software. Explore approaches to drive test automation adoption across multiple project teams and departments, and communicate the real challenges and potential benefits to your stakeholders.