Kent Beck has a perspective on the situation in his book Extreme Programming Explained: Embrace Change. Today I completed reading Extreme Programming Explained: Embrace Change, by Kent Beck , Cynthia Andres. I've come to realize that this notion is at the heart of eXtreme Programming, and it was described in Kent Beck's seminal book on the topic, Extreme Programming Explained—Embrace Change (Addison-Wesley, 2e, 2004). Haven't you got something better to do? I'm not sure whether Extreme Programming Explained : Embrace Change was the book that really started the whole XP thing, but it was certainly the book that started it for me. The term *story* first surfaced in 1999 with Kent Beck's *Extreme Programming Explained*; the definition in the glossary is "one thing the customer wants the system to do."[5] The Planning Strategy chapter explains that a story As David Anderson makes clear in his dense and thorough *Agile Management for Software Engineering*: "In order to maximize the production rate, waste from changes must be minimized."[9]. Not very far into the book, I was surprised to find some advice on "Embrace Change" pre-dating the "Extreme Programming Explained" book which was subtitled "Embrace Change". This books gives a brief idea about the Values, Principles and Practices of Extreme Programming. The first edition is more practical, the second is re-written extensively to show how values fit together with the techniques and practices. Extreme Programming Explained: Embrace Change, by Kent Beck.