At a time when information systems are becoming ever more complex and quality to market and time to market are critical for many companies, a structured test process is essential. Based on their long-term industry experience, Pinkster and her coauthors describe a holistic approach to test management. They show the reader how to set up test projects, how to manage them and how to communicate with the stakeholders. Besides a description of the theory of each activity, each chapters provides as many hints and tips as possible. In addition, helpful appendices contain checklists and templates that support the chapters, and with these, the reader is able to make an immediate start.
Iris Pinkster
Attribut Information Technology (IT) Planning automation cluster control information system management organization project management risk management security strategy testing time
From the reviews:
"While there are many books in the market about testing, there is a paucity of books on the management of this critical area, so the addition of this one is most welcome. The book describes several test strategies, and how these can be leveraged to manage the test process. The general issues with this, and the problems that occur, are described reasonably well, with graphs and charts, which illustrate not only what occurs, but also how and the reasons why. There is also some information about metrics, and how the highly complex test processes occurring today can be measured....no matter how short your short list of management books to read this year is, this ought to be on that list." --ACM Computing Reviews
"There is a prescriptive element in this collaborative book on a test management approach developed … in the Netherlands: ‘Here is The way to do it. Now do it!’… The appendices are very good, and provide helpful checklists. … There is also a clear expression of the roles commonly thought of in testing … . Read this book with a willingness to ask questions, of yourself, your work situation and of the book. … you will find that the questioning pays off." (Software Testing, Verification and Reliability, Vol. 16 (2), 2006)