I particularly appreciated:
- the emphasis on continuously removing impedents to effective work;
- the tips to deal with scaling projects, organizations and teams;
- the comparison between organizations and software. Organizations must emerge and grow in increments, just like software.
- add all tasks to the backlog, not only the functional requirements. However, each Sprint must contains a functional increment.
- the fact that requirements remain complicated even if they are understood by the domain and business analysts as long as they are too complicated for the developpers.
Also, I still find that 30 calendar day Sprints are too long ... I prefer shorter iterations, mostly because of the the queueing theory. Smaller items go faster in the workflow. I believe a project will be faster completed if it is managed into shorter iterations.
But, I do really recommend this book. It made me want to read Agile Project Management With Scrum, also written by Ken Schwaber some years later.