Extreme Programming Explained: Embrace C

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

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

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

Best book

XP explained in the simplest way .

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

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

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.

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.

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.

The book treats much more about how you can improve a project in the political way (not technical). How you can lower the dev to prod cycles, how you can improve code, how to tackle the communication between business and IT, etc ... All this parts when you are technically really good emerge because they are the only painfull. Kent Back gives you a lot of bullets in order to talk with project managers that see only their budget and don't take into account all the human parts. The beginning is not really easy to read but there is so much that it's a real treasure.