Extreme Programming
by Kent Beck /
2017 / German / PDF
1.4 MB Download
I came across this book in the Bibliography section of Scott Berkun's "The art of Project Management". First, the structure. Well, this book is under 200 pages. So when Beck talks about keeping what is essential, he is surely applying it while writing books. Second, the content. The book takes the reader from understanding business risks associated with software development, to understanding the changing economics of software development & why XP can fit the demands of an ever changing business scenario. The book then establishes what XP is, what are its features, what are the activities, who are the X players & then links the roles, activities, & features together across each phase in a typical XP project. While Beck is persuasive about the usefulness of XP, he has also included a chapter at the end of the book which talks about projects where using XP may not be advisable. And yes, such a project is an outsourced development project. XP presents many interesting features. Traveling light - or code & tests together being all you need - sounds like a dream nano-releases - or doing a daily or hourly build so that at any time you have a full system working, no matter the completeness of desired functionality - , building a system story by story, & going back & revisiting scope ever so often are all features that can be immensely valuable to the business & to the project team. As a result of all this, & more such practices, XP resembles to an extent Darwinian evolution in some ways.
