Configuration Management Principles and Practice

If you are going to be working in the field of build and release management, then you will need a good background and working knowledge of Software Configuration Management. This book is the one that I believe will most readily enable you to achieve this. It doesn't look at specific techniques or tools, just what SCM is and why we need to do it.

This volume should be prescribed reading for all IT professionals. Everybody but everybody has an opinion on the merits or otherwise of Configuration Management, but a better understanding would help us all. People not actively part of Configuration Management [CM] will then say, "Yes, it is both more important and more involved that I had thought hitherto". There are five parts to the book; what is CM, the data required for CM, roles within CM, CM in practice and improving CM. The last three are probably the more interesting, but without the first two, it is talking into a vacuum. Throughout, there is emphasis that CM is a tool to be used, and should not become a priority in its own right. Good CM should provide benefits; unfortunately, those who receive the benefits are not always those who have paid the cost (in terms of extra effort and/or information that is required of them). In the first two sections, there is a lot of material that seems repetitive. An example of this is material regarding the naming of configuration items, deliveries, etc. However, this is also an advantage, as chapters or parts of chapters can be read in isolation. I particularly like the use of the same examples in various parts of the text. When referred to, there is usually a diagram, and this is in text, rather than referring to another page in another chapter. Table 15-1 is the same as table 6-1. In books where the diagram is NOT repeated, but the reader referred back to re-read the other section, they never do! Fundamental questions about what to include under the control of CM are addressed (although not always prescriptively answered). What should be included in the CM system? Do you include program source and object code, just source code, or source and the compiler? If the compiler is not included, it may not be possible to amend code for old platforms. Similarly, all tools should be potentially under CM control. Otherwise, a document written is an obscure word processor format may be available in the future, but not the means to even read it easily? There is discussion about the need to capture both physical objects (PC's, memory boards) AND electronic objects. In this case, CM can partly overlap with asset management; it is other ways very different from the latter. However, the author stresses the need to know the boundaries of CM; the defining of a software delivery is not the responsibility of the CM team. Similarly, the use of variants is a design decision, not decided or dictated by those in CM. The latter is essentially an administrative task, concentrating on the four cornerstones; identification, storage, change control and status reporting. The challenges of these four categories are brought out in the latter parts. Most people would agree that documents need to come under CM control at some point. The storage of documents can present challenges, particularly if a master document has many composite parts. There are also needs to take account o

This book lives up to its title by providing principles and practices. What makes it so special to the CM and SCM community is the thorough treatment of the subject in the large, and the attention the author pays to special needs and issues with respect to viewpoints.In the large this book is a tutorial on configuration management, and its sub specialties (project- and production-CM, software configuration management with respect to major software development lifecycle and methodology approaches, and product configuration management). Nothing is overlooked in this book. For example, the detailed discussions of how to align your CM requirements to maturity models and software process improvement methods, and international standards are invaluable to a wide spectrum of readers regardless of whether they are using CMM/CMMI, SPICE, Bootstrap, ISO 9001, US DoD, IEEE or other major standards. This book also offers tailored approaches form implementing CM and SCM for numerous SDLCs ranging from Agile methods to integrated product development to sequential development (and others). I especially like the way core CM and SCM principles are covered to give a baseline of concepts and practices, then how those are applied to environments. In particular, the metrics, organizational considerations in the form of roles, and processes that can be adapted are invaluable. This is one of the best books on CM and SCM I have in my library, and one to which I refer when I need a definitive answer to questions related to practices and processes. In addition to this book I also highly recommend visiting CM Crossroads (ASIN B00009P31G), which has a wealth of additional material that any practitioner - regardless of experience level - will find useful.

Someone finally wrote a CM book that addresses agile development!While the author gives a complete picture of configuration management for all environments, her chapter on CM for agile development is the missing piece of the agile approach. Some parts of this chapter are easy to implement and others not so easy. This is due to the lack of discipline in many agile groups more than unrealistic advice from the author. Easy and necessary: supporting the agile principle of welcoming changing requirements, CM gives the team the ability to control configuration using tools and processes in the book. Delivering *working* software frequently requires a robust CM program so the right components are in the build. This also supports the agile principle that working software is the primary measure of progress. There is too many opportunities for error and rework when CM is not used.Necessary, but not necessarily easy: build projects around motivated people is an agile principle. The problem is too many developers who have embraced agile development think it means getting rid of process. Agile is a process itself, and if you are to deliver working software frequently you need discipline where discipline is needed. CM is one critical area where this holds true. Motivating developers who are sloppy and convincing them that certain processes like CM are essential is the most difficult task to be faced.I've worked in CMM level 3 shops, and am now managing an Agile team, so I've seen this from both ends. In both shops the key to success was CM. Until this book there was next to nothing written about it, and now that this book is available the agile developer and manager have something to guide them. This book will explain how to implement the process, which is something the CVS book does not do well because it is more about using a tool.

Super - this book addresses a very real problem in a very pragmatic way, and gives useful and realistic suggestions on how to solve the real world issues. The book defines an intuitively understandable structure for Configuration Management, which really helps de-mystify this very complex subject. It gives a practical understanding of what can be done, how to decide what to do and what not to do - and then it tells you in detail how to do it! The combination of overview and detail, the completeness and consistency of this book makes this book a must for all software practitioners and project managers.