Books

First of all, (re-)read the Agile Manifesto. Good stuff. It contains a statement of four values (first page) and twelve principles (second page). You can do XP by the book, and follow the practices scrupolously, but if you don't share the values, it probably won't work well.

We split our book recommendations according to Agile Loops.

• Planning Loop Books focusing on user stories, customers, retrospectives...
• Team Loop Books focusing on stand-up meeting, DDD, pomodoro technique...
• Code Loop Books focusing on pair programming, TDD, refactoring...

Feel free to add yours,

Federico, Matteo and Vieri