This book is a very detailed and systematic description of Software Testing aspects as quality plans, SQA components life cycle, and more.
Two major problems:
1. The text is a little captured in the author's imagination - for example, he knows ahead what the client will ask for, etc. You might say, well - he knows what to expect. OK, but here it is so detailed it almost stated the customer's private name and shirt color.
To make it more general: it is not context-driven but best-practice.
Or, in other words, as a person that works as a software tester since 1998, in enterprise companies as well as start-ups and all in the companies in the middle, I never encountered most of the described situations.
2. It is outdated. Although published in 2003, the word Agile is not mentioned at all (Agile Manifesto is from 2001), not Exploratory Testing. So it is not in correspondence with today's world of QA.
It is well written, very deep, thinks of a lot of scenarios, and useless.