You already have taken some basic cost-cutting steps and saved your organization money. Now, you are asked to dig even deeper into your testing budget. Where should you start? You may be looking right at the areas to address and not know what you are seeing or what to do about them. Paul Trompeter explains how to take a fresh look at your existing hardware components, re-examine reliability and availability requirements, and prepare for a future scalable environment. Paul discusses how to get regulatory affairs in order, defuse the ticking storage overload bomb, and streamline testing of complex software systems. For each budget killer, you'll learn innovative ways to overcome budget challenges while maintaining an effective test organization. Discover how to slow the spending of your testing budget while increasing the return on your testing investment and, at the same time, keeping your sanity and sense of humor.
In the coming years, testers will be placed under ever increasing pressure. Joachim Herschmann describes key future trends including the increasing alignment of development and test with business needs, the integration of traditionally separate disciplines, a shared responsibility for quality, and the increased use of testing technology. Joachim describes the experiences of Borland's Linz development lab as a framework for a broader discussion about these kinds of changes and their cultural impact on the organization. He describes the journey from a waterfall-based methodology to an iterative, sprint-based development approach and the integration of developers and testers into a single team of engineers. They found that agile development provided new levels of productivity and value-and posed new challenges of shortened test cycles and a need for new test skills and tools.
Is testing often the last thing considered in your projects? Does your test team always seem out of the loop? Then, Jane Fraser can help you. She describes a process in which testers focus on reaching consensus with the whole project team. With Jane's approach, you work through the requirements and design to document what you plan to test, how you plan to test, and a most important element-what you are NOT going to test. Learn how to reach agreement among developers, product owners, and testers about how the project will be tested before coding starts. In her work, Jane has found that defining the boundaries of the testing upfront has brought the development group closer to the testing group and improved communications about changes and risks. Join Jane to review sample test plans that help improve projects by setting the expectations early.
Although many businesses have successfully outsourced software development and testing activities, managing a truly globally distributed test organization comes with a unique set of challenges. Traditional test processes often break down under the pressure of multiple time zones, varying cultures, and numerous technology issues. Communicating standard test procedures, managing exit criteria, and determining release readiness are all more difficult. Anu Kak provides insight into the practices he has employed in his professional career to manage multi-country, distributed test organizations. These practices range from a one-stop portal for communicating goals and status for all phases of development and testing to opportunities for cross-global teams to collaborate on solving test, development, and automation issues.
Many teams test software on a wide variety of operating system and hardware environment configurations. Traditionally, they use dozens-sometimes hundreds-of machines in their offices and test labs to get the job done. The cost of maintenance of the machines, electrical costs (including power and cooling), and the physical space occupied by the machines all contribute to a budget that can quickly head into the stratosphere. Alan Page describes how leveraging multiple virtual machines on a single host machine will mitigate these budget issues. He shares case studies that show how teams at Microsoft use virtualization to reduce maintenance costs, electrical costs, and machine usage. Alan describes other distinct advantages of virtualization they have discovered, including automatic setup of network topologies. Take back proven tips on when virtualization can benefit you-and, as importantly, when it won't help at all.
Many test organizations believe a new methodology or test automation architecture is necessary to fix problems and make significant improvements in how the business values testing. Molly Mahai proves this assumption wrong as she describes one test team's journey from chaos to credibility. She describes how they overcame the challenges of mistrust between development and test, and management’s skepticism and distrust. By using the techniques of empowerment, coaching, delegation, and some creative group activities, Molly illustrates how small changes-implemented over time-resulted in dramatic improvements for the test team and the overall organization. These changes helped foster an environment where developers and testers work together and management trusts the test group’s work and their assessments. These techniques are easy to apply and require neither more budget nor management approval.
To management, testing often never formally finishes-it just stops. And even before testing stops, we are asked to ensure that our efforts are providing maximum value. However, can we ever really have both efficient and effective testing? More importantly, can we accurately measure effectiveness and efficiency? In the current economic climate, when many test managers have been told to do even more testing with the same or fewer people and resources, the answer to this question is even more important. Lloyd Roden uncovers ways to measure test effectiveness and efficiency and to report these measures to stakeholders with the power, certainty, and confidence that demonstrate the true value testing has within your organization.
As a tester or test manager, you probably have wondered just how important reasoning and rational thinking actually are in many management decisions. It seems that many decisions are influenced by far more-or far less-than thoughtful analysis. Surprise! Testers make decisions every day that are just as irrational as those made by the managers about whom they complain. James Lyndsay presents his view of tester bias—why we so often labor under the illusion of control, how we lock onto the behaviors we're looking for, and how two testers can use the same evidence to support opposing positions. Using demonstrations and entertaining real-life stories, James helps you understand how biases can affect our everyday testing activities. Gain a new perspective on why timeboxes work and why independence really matters.
Strategic alignment between testing and development is vital for successful systems development. Missing, however, have been actionable, how-to approaches for assessing and enhancing this alignment. Jasbir Dhaliwal and Dave Miller present STREAM, the Software Testing Reassessment and Alignment Methodology, a systematic approach used to achieve this alignment at both strategy and execution levels. STREAM incorporates a step-by-step procedure that can be used to: 1) identify symptoms of developer-tester misalignment, 2) analyze and understand the misalignment, and 3) formulate action-plans for fostering stronger developer-tester alignment. In addition, Jasbir and Dave identify specific mechanisms and tools for ensuring that the execution capabilities of testing groups are aligned with their stated strategies. This represents a natural pre-requisite for successful developer-tester alignment.
Jasbir Dhaliwal, FedEx Institute of Technology at the University of Memphis
Although most test managers know they need to improve their processes, many don't know how to go about it. How do you understand the effectiveness of your current test process and then move forward for quick wins and long-term gains? Clive Bates presents a step-by-step approach to gather information on the existing process using special questionnaires and interviews that help you compare your organization with others and identify short and long-term improvement activities. Find out how to package these improvement activities and present them to management and gain their commitment. Once changes start to happen, learn to monitor your testing to determine the impact of your actions and how to properly guide improvement activities. Learn how to conduct project retrospectives, identify what metrics to gather before and after the improvements, and report your successes.