Just my two cents: Preface: A change control/configuration management system usually automates existing policies and procedures for software deployment. They tend to vary wildly from installation to installation. Off the shelf products have difficulty handling all the specific needs of a particular site: Cost-effective compromises have to be made.
My experiences: I have been in five sites where they wrote their own systems. In all cases, the results were satisfactory, full-functioned, right-sized, cost-effective and still in use last I heard. In two cases, I participated in the initial design, implementation, and on-going support; in two others, in enhancement, maintenance and support. At one site, it took the team 1 day to define the requirements and design the command-level interface, a second day to code the core functions, and a week to implement the basic web-based developer interface. Subsequent enhancement, support and maintenance took about a staff-week per year. Conclusions: - Consider the costs and benefits of designing and writing your own change control/configuration management system. - Use an open ended design, with a command line accessible core. - Use a release methodology (per Gartner Group and my experiences): Piecemeal (AKA emergency) deployments mean untested configurations in production . YMMV On Thu, Feb 16, 2012 at 12:53 PM, Ron Wells <ron.we...@slfs.com> wrote: > Looking for alternatives to CHANGEMAN any suggestions to Look at..?? > Pro's/Con's > > ---------------------------------------------------------------------- > Email Disclaimer > This E-mail contains confidential information belonging to the > sender, which may be legally privileged information. This information is > intended only for the use of the individual or entity addressed above. > If you are not the intended recipient, or an employee or agent > responsible for delivering it to the intended recipient, you are hereby > notified that any disclosure, copying, distribution, or the taking of any > action in reliance on the contents of the E-mail or attached files is > strictly prohibited. > > -- OREXXMan
