David Anderson , Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results, Prentice Hall 2004; ISBN 0131424602.
Application of the Theory of Constraints to software development. Each iteration removes a limitation of the system. Work that doesn't remove a limitation is waste.
Kent Beck and Martin Fowler , Planning Extreme Programming, Addison-Wesley, 2000; ISBN 0201710919.
Technical details about the planning process in XP. Real time estimates give more accurate information and a higher level of accountability than the point system.
Fred Brooks , The Mythical Man-Month, Anniversary Edition, Addison-Wesley, 1995; ISBN 0201835959.
Stories to get you thinking about the four variables. The anniversary edition also has an interesting dialog around the famous "No Silver Bullet" article.
Mike Cohn , User Stories Applied: For Agile Software Development, Addison-Wesley, 2004; ISBN 0321205685.
How to plan and track projects feature by feature.
Brad Cox and Andy Novobilski , Object-Oriented ProgrammingAn Evolutionary Approach, Second Edition, Addison-Wesley, 1991; ISBN 0201548348.
Expounds an electrical engineering paradigm of software development.
Ward Cunningham , "Episodes: A Pattern Language of Competitive Development," in Pattern Languages of Program Design 2, John Vlissides, ed., Addison-Wesley, 1996; ISBN 0201895277 (also http://c2.com/ppr/episodes.html).
A discussion of short-cycle programming.
Tom DeMarco , Controlling Software Projects, Yourdon Press, 1982; ISBN 0131717111.
Examples of creating and using feedback to measure software projects.
Tom DeMarco and Tim Lister , Waltzing with Bears: Managing Risk on Software Projects, Dorset House, 2003; ISBN 0932633609.
XP provides many opportunities for risk management, but you still have to manage the risk. This book contains many ideas for taking risks with your eyes open.
Tom Gilb , Principles of Software Engineering Management, Addison-Wesley, 1988; ISBN 0201192462.
A strong case for evolutionary deliverysmall releases, constant refactoring, intense dialog with the customer.
Ivar Jacobson, Magnus Christerson, Parik Jonsson, and Gunnar Overgaard , Object-Oriented Software Engineering: A Case Driven Approach, Addison-Wesley, 1992; ISBN 0201544350.
My source for driving development from stories (use cases).
Ivar Jacobson, Grady Booch, and James Rumbaugh , The Unified Software Development Process, Addison-Wesley, 1999; ISBN 0201571692.
UP contains short iterations, an emphasis on metaphor, and uses stories to drive development. UP is usually document-driven and has less rigorous testing procedures.
Philip Metzger , Managing a Programming Project, Prentice Hall, 1973; ISBN 0135507561.
The earliest programming project management text I've been able to find. There are nuggets here, but the perspective is pure Taylorism. Out of 200 pages, he spends only two paragraphs on maintenance.
Charles Poole and Jan Willem Huisman , "Using Extreme Programming in a Maintenance Environment," in IEEE Software, November/December 2001, pp. 4250.
One team's results of applying XP to product maintenance: 60% reduction in cost and 66% reduction in the time to fix defects.
Mary Poppendieck and Tom Poppendieck , Lean Software Development, Addison-Wesley, 2003; ISBN 0321150783.
Applies the ideas of lean production and lean product development to software.
Jennifer Stapleton , DSDM, Dynamic Systems Development Method: The Method in Practice, Addison-Wesley, 1997; ISBN 0201178893.
DSDM is one perspective on bringing rapid application development under control without giving up its benefits.
Hirotaka Takeuchi and Ikujiro Nonaka , "The new product development game," Harvard Business Review [1986], 86116:137146.
A consensus-oriented approach to evolutionary delivery with implications for scaling projects.
Jane Wood and Denise Silver , Joint Application Development, 2nd edition, John Wiley and Sons, 1995; ISBN 0471042994.
JAD facilitators facilitate without directing, give power to people who know best how to make a decision, and eventually fade away. JAD is focused on creating a requirements document that the developers and customers agree can and should be implemented.