Extreme Programming Explained: Embrace C

Book no doubt is well written to explain Extreme Programming delivery approach. For XP rules you have to go through website though.

This will allow you to understand:Values are more important than code.Its always Process for People and not People for Process.Xtreme Programming is not about long hours in front of PC.Start XP, Start small and let results speak for themselves.Its not about being Productive as a Developer but being Effective.

[book:Extreme Programming Explained: Embrace Change|67833]Kent Beck is one of the guys on that 17 software development practitioners who created Agile Manifesto at the Snowbird ski resort in Utah, which includes the likes of Ken Schwaber and Jeff Sutherland who created "Scrum"In my own words XP is a flavor to add to Agile Project and Programming Practices. You can say it extends your knowledge of scrum and agile. This book comes from its creator Kent Beck. Would say a good one time read. If you already know Scrum and Agile, you can just skim this book.Agile way of working=(Scrum, Kanban, XP, SAFe) Project Managers and Product Managers will surely be benefitted by understanding the basics of these concepts. This book is i guess both necessary and sufficient to understand XP.

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

XP explained in the simplest way .

Best book

Kent does a.briiliant job in explaining the process. his way of articulating is commendable. juzt thatt he could have given a step by step of how to get started with xp. that woud have helped a lot

Really good book - anyone wanted to understand XP... this book is highly recommended

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.

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

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 funzionanteSi 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.

Extreme Programming is not so extreme after all. It is the extremely imbalanced world that makes it extreme. Whenever you try to be good in the truly moral sense of the word, you can’t help being perceived as extreme.

Tolles Buch