The book focuses more on the technical aspect of the software delivery. It discusses more on the challenges in the software development/ delivery perspective. One area I liked most is the maturity model for configuration. I think this model is a handy tool to evaluate the effectiveness of the delivery process of your own production line. The book also stress the fact on automation all aspects of the delivery process as much as possible and the key role identification of the members and methods to ensure that the teams are not working in isolation. One of my key learning out of this book is the team correlation and work planning. In practical sense, specialization and work effectiveness, log bug rate, and shorter delivery cycles with speed feedback can be achieved with the individuals in the pipeline are more focused in few core activities rather than overloaded with many different activities. Also another interesting fact authored that I'm also in believing is to keep the documentation of the product as much as minimal as said in this book as "documentation also has a nasty habit of going out-of-date" and only proved to be good for ISO 9001 which, in my perspective is have a greater truth.
This book would be better if they could also address the road mapping and delivery for very complex global products. I was expecting few tips and practices on this line. It would be great if the book had some chapters on requirement design integrating with change management and how effectively it could be integrate into total value delivery chain.
Recommend this book for you if you looking out the delivery chain from more from technical background.