A breakdown of how these practices can drive development
What this book is not:
A collection of hard fast rules
A railroad
A solution to every problem
Software development practice is such an odd animal that trying to create a hard fast rule to solve problems doesn't work. That is why agile was created, to solve common problems, create visibility and align the team. This book describes this paradigm very well. I am happy to cherry pick the things that *I* need (or can get away with) for my projects. This book tries to explain those things and how they can impact your process. SCRUM, XP, TDD, and CI work. That is a fact. They just don't work the same way for every project.
Ссылка удалена правообладателем ---- The book removed at the request of the copyright holder.
