Software Release Methodology

Excellent details for SCM/CM strategies. Starts off with a couple of chapters for beginner's to SCM. Then covers every aspect of Release Process. The chapter on integration process was detailed like no other SCM book that I've seen. The book explains concepts of software development from the perspective of a Release Engineer -- from source control branching/merging strategies, to build control, aspects of development cycle, then to product release. One of the better CM SCM books out there. None of the others SCM books look at it from a Release Engineer's perspective like this one. If you are already passed the basics of SCM then this book will complete your training.

This book integrates SCM and application delivery/service delivery promotion and release processes in a single book. The highlights include: (1) clear descriptions of software configuration management processes and strategies, (2) exit criteria for release of software into production, and the macro view of all of the relationships between and among development, QA and production.Chapters I particularly like include 5, Defect tracking, which can be used as the basis for an integrated issue management system specification; 6 and 7, modularized system integration and change control, which ties together the processes necessary to interface development and production - two different aspects of IT that seem to be on different planets, and 8, release classifications and numbering, which provides a sane and logical numbering strategy.As a 25+ year veteran IT professional I learned much from this book, and found the material equally suitable for IT professionals across the full spectrum of skill and experience levels. This is a one of a kind book that bridges development and production, and will give practitioners in both organizations a common vision and insights into the challenges and requirements that are unique to each group.

While the information packed into this remarkable book seems like common sense, making it happen is not easy and deeply understanding the many nuances and practical examples and advice is anything but trivial.The author has provided a clear and methodical approach to software configuration management, release management and metrics. If you are familiar with goal-question-metric planning you will see the elegance and value of this book. Although the author does not use GQM explicitly, the processes and integration of those processes are fully supported within the GQM framework.This book is complete and thorough and goes well beyond commonsense. As an example, the chapter on release and version numbering gives one of the best approaches I've encountered, and the end-to-end processes are anything but basic. They are a blueprint for getting to CMM level 3 and about in a number of KPAs, including project management and quality assurance. This book only appears simple to simple-minded people. Experienced professionals who understand the difference between theory and the challenges of real life will see this book as one of the most valuable resources they can own. Additionally, you would have to buy a pile of books, then soft through them to get the same comprehensive approach that the author progives between two covers. If you are a professional who is concerned about process and effective SCM and release management this book is essential.

This book goes far beyond traditional books on SCM by providing a methodical, complete view of the capture, versioning, build and release process. While the author focuses on what must be done to safely release a software product into production, he also provides the necessary steps to assure product quality and integrity. Key milestones covered include defect tracking, change control and release tracking. These three areas, to the best of my knowledge, are not covered in any real depth in most SCM books, and are welcome additions to the applications delivery body of knowledge.I like the way the material is presented. As a consultant who has developed processes and procedures in support of release management I can attest to the fact that describing the capture, versioning, build and release process is not an easy task. The author has done a remarkable job of separating out the pieces, focusing on each piece as it relates to the whole, and crafting a big picture that you can drill down into for details. Another thing I like about the book is the standalone nature of each chapter - you can safely skip to whichever chapter interests you the most without getting lost. Who should read this book? The following come immediately to mind: Build and release managers, software configuration managers, developers who need to understand the processes for which they are responsible for complying, production services personnel who receive applications into production after the release process is complete (actually, this group participates in the release process), SQA professionals and project managers who also need to be aware of the release management process. In particular, the SQA group will find the chapter on defect tracking extremely useful for developing a strategy for metrics capture, analysis and action. Project managers will find the entire capture, versioning, build and release cycle description in the book useful for adding appropriate tasks and deliverables to project plans. If you follow the author's cycle you will make sure that every milestone, task and deliverable in a development project is accounted for. It is also invaluable to production services staff who will be receiving applications into productionThis book easily earns five stars for the following reasons: (1) it is the only book of its kind, (2) it is complete and covers every imaginable detail, and (3) it addresses topics that are of interest to a wide audience.

As the author has observed these fields binding together so have I. I have searched on numerous occasions for texts that provide a unified perspective on these fields. Now I finally have it. The book does a great job of stepping through the mine-fields of SCM, defect tracking, and project management which have collectively been nothing but a disaster in my experience in about 6 software companies. While the book does not go into a low level of detail on the SCM models, as I would like I believe that it does a good overall job of the fields. Hope we can see more from this author in the future.