处理变更管理的最佳方法是什么? [英] What is the best way to handle change management?

问题描述

我组织的主要项目在星期一上线.那是我在这里的第三天.现在我已经待了将近一周的时间，我的任务是创建一个变更管理计划，以维护应用程序并准备阶段2，该阶段将在某天"开始.我们是一家Microsoft商店，但是胸襟开阔.

My organization's main project went live on Monday. That was my third day here. Now that I've been here almost a week, I'm tasked with creating a change management plan for the maintenance of the application and preparation for phase 2, which will commence "someday." We're a Microsoft shop but open-minded.

我正在寻找有关CM技术和尤其是工具的建议，以帮助解决这一问题.我熟悉ITIL，并且一直在考虑如何将CM的概念应用于该项目，但是请记住，这个项目比我以前习惯的要小得多(<100个用户与数千个用户).我不确定如何或是否可以将ITIL缩减为这么小的项目.也许我在想的太小.

I'm looking for some suggestions on CM techniques and especially tools that will help with this. I'm familiar with ITIL and I've been considering how its concept of CM could apply to this project, but admittedly this one is a lot smaller than I'm used to (< 100 users versus thousands). I'm not exactly sure how, or if, ITIL can be pared down to such a small project. Or maybe I'm thinking too small.

您的组织如何在系统级别管理变更?对你起作用吗?怎么改善呢?

How does your organization manage change at the system level? Does it work for you? How could it be improved?

要进一步澄清，有人可以推荐CM流程和工具，也许是从开源或敏捷世界来的?

To further clarify, can anyone recommend a CM process and tool, perhaps from the open source or agile worlds?

推荐答案

建立一个评审委员会，由来自开发，运营，质量保证，业务等部门的高级代表，以CM经理为主席.所有更改都必须提交给董事会.

Establish a review board, with senior representatives from development, operations, qa, the business, etc., with the CM manager as the chair. All changes have to be presented to the board.

在我工作过的一个地方，您需要获得一致批准才能实施更改.在另一个人中，只有2/3的多数票就足够了.但是，在这两个地方，提出更改时都必须团结一致.您真的不希望自己毫无准备，看起来像个傻瓜.

In one place I worked you needed unanimous approval to implement a change. In another a 2/3 majority was enough. At both places though, you had to get your s**t together when presenting a change; you really didn't want to be unprepared and look like a fool.

CM小组定义了通过控制门所需的工件"，通常是一系列以清单为指导的表格.如果系统是关键任务"，您可能还需要进行某种类型的CM审核，以确保遵循了您的开发流程(运行了单元测试，文件处于版本控制下，使用注释正确标记，QA测试已签名等) ).

The CM team defines the "artifacts" required to pass the control gate, usually a series of forms with a checklist as a guide. If the system is "mission critical" you may also want to do some kind of CM audit to ensure that your development process was followed (unit tests were run, files placed under version control, tagged properly with comments, QA tests signed off, etc.).

对于工具来说，通常一个简单的电子表格或数据库就足够了，您可以根据组织的流程量身定制一些东西.保持简单.

For tools, a simple spreadsheet or database is usually enough, something you can put together yourself, tailored to your organization's processes. Keep it simple.

CM经理还必须具有一些牙齿"，并且能够执行审查委员会的决定. CM是一个质量过程，可以确保维持质量标准，而不是确保按时完成.

The CM manager also has to have some "teeth" and be able to enforce the decisions of the review board. CM is a quality process, and is there to ensure that quality standards are maintained, not that deadlines are met.

这篇关于处理变更管理的最佳方法是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！