Rating: 
Summary: Great overview of these collective fields
Review: 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.
Rating: 
Summary: Fundamental techniques for releasing a software product
Review: Concentrates on issues related to the delivery of a product such as builds, numbering, distribution, and release planning. Addresses topics associated with a high quality delivery such as source code control, issue tracking, modularized development, and change control. Use this reference to compare your release process with the conventional approach. Excellent discussion of branch management and branching strategies for version control systems on pages 23-32. Explains the usage of a current product tag and a system integrator tag on pages 100-103.
Rating: 
Summary: I have only skimmed through this book, but
Review: Have you noticed that in a book about release methodology, they have forgotten to release a part of the book? There is a title, it's in the TOC, and a few pages even serve as a placeholder, but the Index is simply missing. At least in my copy of the book... oops.
Rating: 
Summary: Contains trivial facts everybody knows
Review: I bought this book, because of the great reviews, but I must agree with the comment "If you know ANYTHING about developing software...ANYTHING at all...this book is a complete waste of time." Area of release planning IS interesting and difficult, but solution is not this book.
Rating:
Summary: Ok as reference book for Pointy Haired Managers
Review: I went out and got a copy of this book because (1) relatively good initial reviews, (2) the items in the Table of Contents that made sense. Although the content does not suck as badly as what the other reviews wrote, it wasn't "satisfying". Bays placed in sections of text assuming the readers do not an inkling of a tech background, and no idea whatsover on the psychology of a software shop. It's nice to see in print all the psychological/organization behavior assessments you've made through years of painful lessons, but I needed a book that will tell me practically what to do (or at least a story about what worked for him and what he thinks one should do in different set ups). No, instead he launches into a textbook style discussion of a lot of basics with the assumption that the reader have never gotten been down in the trenches as a /with the developers before.It's not an entirely bad approach. Like I said in the title of this review, this book is great for "Pointy Haired Managers" (ala Dilbert) -- managers of tech organizations who have never been in the trenches himself. No sarcasm intended. It's also a good book to use when you have to educate/convince "Pointy Haired Managers" on how things "should be" done (because it sounds really illogical from his simplified point of view). No sarcasm intended here too. (Those who have worked with non-technical bosses will agree with me the hardest part is educating a boss with a slight tendency to micromanage -- because he couldn't grasp the situation.) Actually this book can be a great text book for an IT Technical Management course for non technical managers. It does have everything you need to know about the last stages of software development (THE RELEASE).
Rating:
Summary: Ok as reference book for Pointy Haired Managers
Review: I went out and got a copy of this book because (1) relatively good initial reviews, (2) the items in the Table of Contents that made sense. Although the content does not suck as badly as what the other reviews wrote, it wasn't "satisfying". Bays placed in sections of text assuming the readers do not an inkling of a tech background, and no idea whatsover on the psychology of a software shop. It's nice to see in print all the psychological/organization behavior assessments you've made through years of painful lessons, but I needed a book that will tell me practically what to do (or at least a story about what worked for him and what he thinks one should do in different set ups). No, instead he launches into a textbook style discussion of a lot of basics with the assumption that the reader have never gotten been down in the trenches as a /with the developers before. It's not an entirely bad approach. Like I said in the title of this review, this book is great for "Pointy Haired Managers" (ala Dilbert) -- managers of tech organizations who have never been in the trenches himself. No sarcasm intended. It's also a good book to use when you have to educate/convince "Pointy Haired Managers" on how things "should be" done (because it sounds really illogical from his simplified point of view). No sarcasm intended here too. (Those who have worked with non-technical bosses will agree with me the hardest part is educating a boss with a slight tendency to micromanage -- because he couldn't grasp the situation.) Actually this book can be a great text book for an IT Technical Management course for non technical managers. It does have everything you need to know about the last stages of software development (THE RELEASE).
Rating:
Summary: For those who know a little and want to know a little more
Review: I you know nothing about software development, you will not understand what he is trying to say. (You will be lost even in the beginning, chapter 2 "Nontechnical Primer on Files, Tools, and Source".) If you are already a seasoned software developer (or release/build engineer), this book will be of very little use. (chapter 3 "Source Code Control", chapter 4 "Builds", chapter 5 "Defect Tracking", etc. are nothing really new to you.) I give this book 3 stars because
1. it's very hard to find a practical book on SCM and release management
2. Michael Bays has included somewhat useful real-life methods used in Cisco
3. If you know a little and want to know a little more, this book is OK Having said that, after reading the book, you will still not be able to develop an entire CM, build, and release infrastructure for medium to large software development. One complete infrastructure sample each for small, medium and large software development environment would gain this book 0.5 to 1.5 more stars.
Rating:
Summary: For those who know a little and want to know a little more
Review: I you know nothing about software development, you will not understand what he is trying to say. (You will be lost even in the beginning, chapter 2 "Nontechnical Primer on Files, Tools, and Source".) If you are already a seasoned software developer (or release/build engineer), this book will be of very little use. (chapter 3 "Source Code Control", chapter 4 "Builds", chapter 5 "Defect Tracking", etc. are nothing really new to you.) I give this book 3 stars because
1. it's very hard to find a practical book on SCM and release management
2. Michael Bays has included somewhat useful real-life methods used in Cisco
3. If you know a little and want to know a little more, this book is OK Having said that, after reading the book, you will still not be able to develop an entire CM, build, and release infrastructure for medium to large software development. One complete infrastructure sample each for small, medium and large software development environment would gain this book 0.5 to 1.5 more stars.
Rating:
Summary: The Proven path to Software Release
Review: SCM and Software Release Management encompass a broad spectrum of activities and practices that ultimately determine the quality of the product and the control of the product release. Software configuration management (SCM) and Release Management may sound the same; 'Software Release Management' by Michael E Bays lucidly provides an insight into what are the nuances.
Software configuration management is a key process area, which holds a significant importance in determining the control and success of the delivery process. Right from source code control, build management, defect tracking, change management, to multi-platform product releases, determines to a great extend the release process management methodologies that gives a structured approach to software development, that ensures that the efforts of the development team doesn't go wasted in providing the right versions and a more complete solution to the end-users.
The significance of software release management comes more to light in large projects involving large team, multi-site and multi-platform development. Full life-cycle projects which usually reflects wide gaps and variations between what is initially defined and what is finally delivered, demanding stringent and documented processes which control the requirement changes, defect fixes and change control mechanisms to the minutest possible detail. Michael E Bays captures in the most simplistic coverage, how this can be executed by proper release mgt methodologies. This calls for an efficient defect tracking and configuration mgt systems, to determine whether 'what we believe, is what we achieved'.
Rating:
Summary: One-of-a-kind book on an important process
Review: 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 production This 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.
|
