How to manage a large software project is a perennial problem in practical programming. Here the authors offer advice based on the so-called agile approach. They heavily dump on the traditional waterfall method, as being too coarse grained and liable to lead to projects being too late or, equivalently, not meeting all the requirements.One interesting touch they add is a recommendation to start your project with open source code, whenever possible. There are indeed differences between typical agile software processes and open source development projects, as the book acknowledges. Open source rarely has budget constraints [everyone's donating free time] or often even a schedule. How many commercial software projects, agile or not, can say this?
There is also a chapter devoted to pair programming. This has been the distinguishing feature of Extreme Programming, and much derided by critics. But the book's take on pair programming is a nuanced difference from that espoused by XP. Perhaps worth a careful read, even if you don't end up fully agreeing with the authors.
Product Description
This book is a comprehensive and thought-provoking introduction to some of the most advanced concepts in current software management. The authors demonstrate how software development rhythms can be harmonized to achieve synergies, making them stronger together than they would be apart. It offers readers practical guidance on how to take the themes and concepts presented in this book back to their own projects to harmonize their software practices and release the synergies of their own teams.
Click Here to see more reviews about: Software Development Rhythms: Harmonizing Agile Practices for Synergy (Hardcover)
No comments:
Post a Comment