The author applies standard project management techniques to object-oriented projects. In particular, the assumptions and techniques underlying UML and the Unified Process are to be found in the various chapters in the book. For example, the author advocates managing complexity by using packages, use cases, encapsulation, inheritance and aggregation.
The main strengths of the book are: It attempts to integrate OOT with project management techniques using the standard UML and this integration process lasts for the duration of the full software lifecycle.
The book may or may not be useful depending on what you are looking for. For example, it is (very) superficial in places and in general I would say that it lacks 'meat' in the following places:

Traceability issues
Useful checklists and tables
Quantitative treatment (measurement)

Furthermore, the chapter on lifecycle models is not convincing. The author suggests that we should NEVER use the Waterfall model while he suggests that the Controlled Iteration model. Why? I have not understood this latter model when reading the boook. I think that it is too complex.

Concluding, this book serves as a baseline for further research and should be complemented by other sources, for example from Boehm, Air force and IEEE.

Finally, the title is an attention-grabber and in my opinion incorrect. Project management is independent of the technology used (in this case OOT). A better name would have been "Project management of software projects that use UML".