I object to the unnecessarily harsh review being given to these authors for their excellent work.
Read the subtitle: "The Latenight Developer's Handbook"
In case you missed it, the authors state it again, on page xvi:
"The book does not discuss theoretical aspects of configuragtion management because we think that inaccessibility has been on of the barriers for broader use of configuration management."
Precisely.
Years of experience? Combined, the authors have over 38 years of practice and MANAGEMENT experience.
And I object to the presumption that it should be used only by small-project teams. This book is listed by the W3C for use by their developers, which is one of the largest collaboration efforts in history.
If you're looking for a textbook with which to teach a class, you may still want to consider whether you want to present "Big Science" configuration management to your students right away. Don't you have an obligation to prepare them with the survival skills they need in industry, before moving on to other topics you personally find more interesting?
These authors deserve better, with their multi-decade experience in bringing software products through the release cycle to the general marketplace, which are even now in day-to-day use by many organizations both large and small.
Put a cover on this book; you're going to wear it out referring to it with your colleagues.