Most Scrum teams adopt XP terminology and practices, so I think you'll find the book very compatible with what you'll be doing. We have a cross-reference early in the book that shows how the Scrum practices map to the practices in the book. The practices in the book are a superset of Scrum's practices.
James Shore, coauthor of <a href="http://www.amazon.com/Art-Agile-Development-James-Shore/dp/0596527675" target="_blank" rel="nofollow">The Art of Agile Development</a>. Website and blog at <a href="http://www.jamesshore.com" target="_blank" rel="nofollow">http://www.jamesshore.com</A> .
In fact, Scrum is a pure project management method - it doesn't tell you at all how to actually build *software*. Many Scrum teams adopt their engineering practices from XP.
The project management practices of XP are quite similar to Scrum practices, but often are referred to by different names.
So reading the book might not the best way to learn the terminology your team will be using, but from what I've read from the early preview chapters, it's a great way to learn how a well working Agile team will function.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Story like this gets better after being told a few times. Or maybe it's just a tiny ad: