Extreme Programming Explained: Embrace Change, 2nd Edition (The XP Series)

This book is more of a philosophical way of describing how to embrace change and adapt to the more collaborative and time sensitive approach to managing a project be it software or organization. Author provides very simple practical examples that elucidate complex concepts, and this approach not only simplifies intricate concepts but ensures reader can easily follow, connect and comprehend the subject matter. Authors could have provided some code samples along with theoretical and philosophical explanation other than that this book deserves 7 for 10 grading. Enjoyed reading the book and I would suggest this book as a must read for developers or anyone who wish to incorporate quality and embrace change in executing projects in non traditional way.

Required for an XP (Extreme Programming) class. The book was only used for the first three weeks of classes, so I didn't read it in too much depth. This book isn't too bad, it has a lot of obvious information (ie, treat coworkers with respect) and it doesn't offer too much in terms of insight. But despite those issues it's not a bad read, it does have some good information, just nothing ground breaking. Do not get this book if you're looking for anything ground breaking or anything enlightening, if you're interested in agile development, this book may be worth it to read through however.

I bought this book to remind me of the excellent principles, practices and values of Agile that made this methodology work. It was a great refresher.

I bought this book to help with my study for the PMI-ACP certification exam. Part of the recommendations suggests that you understand Extreme Programming inside and out and how it relates to SCRUM and LEAN. This is an excellent book written by Kent Beck, the person who brought Extreme Programming to the forefront of software development. It is easy to read and understand and covers the subject matter very well. Whether you are studying for this exam or whether your team is adopting Extreme Programming, this book is for you.

Book is in good condition and meets my expectations. Reasonable price. Quick delivery. All around good value and good buying experience. Would buy from vendor again and recommend that others use this vendor as well.

I found this book quite inspiring, let alone its value for concept explanation. I do not agree with some of the ideas, but this book doesn't try to sell you each and every practice, in my opinion, so it's ok

I have been a programming hack for many years. This book along with a couple of others that I have read in the last six months or so have opened my eyes. I knew that basics were not my strong suit. I am entirely self-taught with desktop programming. I just knew there were things that didn't seem right. I always had close contact with my customers, knew from early VB experience that you could make a mess of code, that defects could bury a project. XP explained by one of the founders, maybe The Founder just lays it all out. Now still I am a single man shop, so really I am now starting practice on PXP, Personal Extreme Programming, but it will be the only way I practice from here on!

I remember reading a copy of an earlier edition of the Extreme Programming Explained: Embrace Change, 2nd Edition (The XP Series) back in the early 2000s. At the time, the book seemed revolutionary amidst my professional work in the waterfall methodology. In my opinion, it was so groundbreaking because it was the first time I'd heard anyone try to manage the software development lifecycle as something other than just another generic project. While there are similarities in software design to other types of custom manufacturing, XP is much better attuned to what makes software design DIFFERENT. So why three stars? My company is in the process of a transition to a flavor of agile programming. It was decided that, in an effort to give everyone a common set of concepts and vocabulary, that this book be taught to our entire department. The issue, as I see it, is that as the grandfather of modern agile methodologies, XP is very important. However, as important as understanding how XP came to be is, agile has moved on to more developed/evolved methodologies. This book does not get you to TDD, or advanced CI/CD. It does not get you to Scrum, LeSS, or Kanban. However, if you want this book as a historical guidepost of "how we got here", I think it's decent.

Uma das melhores literaturas se você quer levar seu trabalho como engenheiro a outro nível é formar times de alta performance!

Llegué a este libro por recomendación y recomiendo que me ha encantado. Fácil de leer y muy ameno. Inicialmente estaba a la defensiva por pensar que era una nueva teoría del desarrollo de mucho pensar y poco hacer y es justo lo contrario. Si quieres ser un buen programador y quieres realizar proyectos de calidad necesitas leer este libro e interiorizar sus conocimiento, es una teoría que funciona.

If you already know XP, you perhaps want to know whether to buy this book. I'll try to answer that question. The first edition of this book marked a watershed in the way I thought about software. I did leave many questions unanswered, however, as our team struggled to implement the practices 'out of the box'. Perhaps a bit too much revolutionary zeal. The breadth of the second edition is far greater. It explains the principles so that you can adapt them to your own circumstances, without subverting their original intent. As such it is a far more usefull book than the first edition, even if it lacks the bold audacity of the former - or maybe the ideas of XP dont seem so left of field anymore.

Read this book very carefully. And then repeat. Again and again. It brings sense and life to SW development!!

Utile ed esauriente trattato sul Extreme Programming. La tesi principale proposta è che non ha senso cercare di fare previsioni che non possono basarsi su niente altro che l'incertezza. Piuttosto, Kent Beck propone una metodologia che abbraccia i cambiamenti invece di combatterlo. Gli aspetti principali della metodologia sono: - pair programming che porta ad una maggiore qualità del codice scritto - pianificazione flessibile: scegliendo giornalmente ciò che va fatto in base alle priorità del momento - design for change - non trattare nessuna parte del progetto (comprese le specifiche) come immutabili, essere sempre pronti a modificarli quando necessario, - il codice è la documentazione e quindi va scritto in modo che possa essere facilmente utilizzato come tali, - unit test: gli unit test sono uno step essenziale per fornire codice funzionante Si può essere d'accordo su tutto o su parte dei punti in elenco o altri aspetti del libro. È sicuramente importante prendere coscienza del problema di fondo, la pianificazione fondata sull'incertezza e provare a prendere ragionare, magari prendendo spunto proprio dalle linee guida di XP. Libro stra-consigliato.