Foreword by Hans Schaefer

Another book about test management, do we need this?

If you have read many testing books before, then maybe not. But, if you want to learn about test management, and have not read so much yet, then the answer is definitely yes. This should be the first book to read for a new test manager.

Why do I like this book?

This book is short and to the point. It contains the things a test manager needs to know, without all the extra ballast. It helps people to plan and control the testing effort in many projects, with no restriction as to what kind of software is developed. It does not make a science out of the practical skills to manage a testing effort. It greatly helps to prepare for the ISTQB Advanced Level – Test Manager exam, and people do not waste time reading a lot of unnecessary other stuff. The book covers the current ISTQB Advanced Level syllabus, as well as most areas of the draft 2007 version of the advanced syllabus. It should be possible to pass the ISTQB exam based on studying the book.

The application example used throughout the text is the same as in the earlier Software Testing Foundations book, thus making reading a lot easier for the continuing reader.

Chapter 9 about risk-based testing is probably the most important chapter. The language of test managers should revolve around risk. Risk is what stakeholders understand. Testing should measure the residual risk in an application.

But there is a lot more to this:

As test execution comes last in any project, the testing phase will always be under pressure. Often, the option to delay delivery is not open, thus the test manager must know how to prioritize and manage all the problems inherited from other people’s work. Doing this proactively helps a lot. But, not only must test execution get differing priorities; there are also risks to the test project itself. Many of these risks are shown in the book, together with examples of how they can be overcome or dealt with. However, I would have liked to see more details about how to prepare for project risks to materialize. This might, however, be too special for this book.

Chapter 7 deals with process improvement. Several industry standard models are described. With this book and just a few more references, the reader should be able to execute an initial process assessment and find some important improvement ideas. However, one method is described in less detail: Examples for root cause analysis of defects, especially defects found too late, i.e., surviving the testing effort. However, this is a flaw in the ISTQB syllabus and thus outside the scope of this book.

The other chapters in the book contain the more conventional tools for a test manager, such as a description of differing application development models and the place of testing within them; issue tracking and handling; use of metrics; configuration management etc.

The trouble in other literature is that one often needs several books, not just one. Thus, this single book is effective for its readers.

Get it, read it, think through it, and pass the ISTQB advanced test manager exam!

Best regards,

Hans Schaefer
Leader, ISTQB Norway
Software Test Consulting