We started our SW outsourcing last year with an office set up
in China. Though we gained lots of experiences through painful
trial process, I think we would have saved much more time and
energy on both business and technical sides in dealing with our clients, should we owned the book earlier (we did not buy that from Amazon unfortunately)

Since the author was a one time insider of the well known, NASDAQ listed Indian SW outsourcing company, along with his rich academia experience, the book is full of a ciombnination of engineering praticalness and acdemia sophiscation, and is well orgnized and well written. It touches not only the state-of-the-art, like tracability, impact analysis, risk management, SW metrics and effort estimation, but also addreess pratical issues like contract/agrement drafting and negotiiation, which we found is very useful.

One thing confuses me is that asides from most of start-of-the art techniques adopted by InfoSys, why they use a revised Waterfall process model instead of popular evolutionary process.
Is that because they are in the SW outsoucing busienss?

Another suggestion is that, the book may looks like better
if it can adopt a evolutionay/iterative/incremental way on
telling people the story and the theory/practice behind them.
Some popular books on UML are using this Unfidied Process
way, evn on writing books. Is that interesting?

In my openion the "Guidelines for improving the software process" written by Carnegie Mellon university (SEI) is a good book to be referenced as a CMM standard and the "CMM in practice" is a good reference book to know how the KPA's can be interpreted and implemented in an organisation from a practical standpoint.

Due to the almost inexistant (affordable) professional training available in the subject of CMM, books such as this goes a long way in filling that gap. However, i would say that this book throws light till level 4 only. If you are looking at guidance to implement level 5 KPA's this is not the book.

The examples given are quite clear and helps understand the requirements of CMM better.

Its approach is clear, pragmatic and logical. It covers most of the important issues in CMM, from planning to closure of software projects, giving examples of a real-life project where they are needed.

If you are a beginner and want to embrace best practices and standards, I would recommend you to study this book first, and then The Capability Maturity Model. You will be surprised how clear it will appear to you. Same for ISO practitioners, especially ISO 9000/2000, which contains many more requirements on SPC compared to ISO 9000/94.

If you have been working with CMM for a while, reading this book could give you a better understanding of it.