What similarities does your book have to the Coplien book Organizational Patterns of Agile Software Development and to the Shore/Warden book, the Art of Agile Development? (Looking at the table of contents, it would seem to have more in common with the latter.)
How does your book differentiate itself?
Would you recommend the book for *everyone* associated with an agile project?
The easy one first, Jim Coplien's book on Agile patterns takes a look at the "what is?" question. He defines stand up meetings and other practices. My book is about adopting practices and therefore addresses the "how to?" question. Once you've decided you want to do stand up meetings, how do you get to the point where you are successfully practicing them? What business value should you be getting from a stand up meeting? And, just as importantly, what common pitfalls are there? The two books are orthogonal.
Now, as for Jim Shore's book, there are a couple of distinguishing factors. The first one is that my book starts off by focusing on business values and process smells before discussing a single practice. This is very important, we set the goal first before we go about adopting and adapting practices. The patterns catalog in my book also acts as a reference with clearly delineated sections about business value, applicable contexts, a step-by-step sequence for adopting practices, and - extremely important - a smell's section describing how others have gone wrong adopting the practice.
I can go on and on tooting my own horn But that wouldn't be very productive Let me point you to a few reviews where other's have commented on the book and one person in particular brings up Jim Shore's book: