Mon premier blog

Extreme programming explained: embrace change Cynthia Andres, Kent Beck
Publisher: Addison-Wesley Professional

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]. I'm also spending hours coding Java in Eclipse with JUnit. Pro .NET 2.0 Extreme Programming. Addison-Wesley, Upper Saddle River, NJ (1999). Extreme Programming Explained: Embrace Change, 2nd Ed. I doubt you would be doing this work were it not for some other psychological abuse you are trying to avoid: loss of job, loss of status, loss of face. Kent Beck has a perspective on the situation in his book Extreme Programming Explained: Embrace Change. Tilt one way or another and you'll look more like a comet than a programmer. Haven't you got something better to do? Today I completed reading Extreme Programming Explained: Embrace Change, by Kent Beck , Cynthia Andres. Palmer, S.R., Felsing, J.M.: A Practical Guide to Feature-Driven Development. The Art of Agile Development (Shore & Warden); Agile Java (Langr); Extreme Programming Explained: Embrace Change (Beck); Test Driven (Koskela). This books gives a brief idea about the Values, Principles and Practices of Extreme Programming. Beck, K.: Extreme Programming Explained: Embrace change. 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.