Simple rules are great for guiding us through an overwhelming workload. Sometimes complicated solutions are necessary, but simple rules often outperform complex algorithms, making them more efficient than sophisticated, difficult flows. They can also break down big goals into practical daily guidelines testers can follow to perform more effectively. Let’s see how simple rules can be applied in software testing.

The test team uses the test automation system to execute thousands of test cases because … why not? The tests are running automatically, for free, so there is no incentive to improve test efficiency. Just run them all! But eventually, as more and more tests are added, the system becomes overloaded. Test runs are delayed and you get a bottleneck. Don't throw more money—or new systems—at the problem; do this instead.

As an advocate for quality, you look at the product, take into account time, budget, and other business constraints, and recommend fixes to ship a product with the best possible quality. ... And the businesspeople in production don’t want to fix it. How can you communicate bugs and risk to people who don't want to listen? Instead of getting frustrated, you need to frame issues in a meaningful way—and, if you have to, let people fail.

Testing has changed a lot in the last ten years. Although some traditional techniques are still useful, many testing activities are being done by developers, users, and other nonprofessional testers. Consequently, the role of test manager has changed into more of a test assurance officer and coach. The way this new role is implemented can differ from situation to situation. Here’s how it can be useful.