The most important one is this: http://agilemanifesto.org/ http://agilemanifesto.org/ Yes, it is only 3 paragraphs and a title, but if you want it in book form

The most important one is this: http://agilemanifesto.org/ http://agilemanifesto.org/ Yes, it is only 3 paragraphs and a title, but if you want it in book form you can print it out and put it between some covers. The important thing is to read those 3 paragraphs carefully and to think about them. Avoid getting caught up on the bandwagon of some management methodology that claims to be Agile, because it probably isn't. And read Clean Code by Robert Martin, one of the writers of the Agile Manifesto. One of the things encouraged by Agile is TDD, that is to say, a cycle of coding that starts by writing a failing test, then writing code to pass the test and then refactoring code to be better according to principles like DRY and YAGNI. If you work in this Red-Green-Refactor cycle, then you will have a tough time when faced with a tangle of spaghetti code written in Java or C++. That's when books like Working Effectively with Legacy Code by Michael Feathers come in handy. In general, steer clear of books about Agile, and focus on books that teach something real, but happen to fit into the Agile Manifesto philosophy. Talk to some developers that you know are truly Agile developers, not practitioners of a methodology, and ask them for book recommendations.