配置管理中CCB的建设
2008-03-09 09:44
197 查看
The Change Control Board (CCB) represents the interests of program and project management by ensuring that a structured process is used to consider proposed changes and incorporate them into a specified release of a product. The CCB shall request that impact analysis of proposed changes be performed, review change requests, make decisions, and communicate decisions made to affected groups and individuals.
l Scope of authority
Indicate the scope of decisions that the CCB makes. This scope could be over a specific organizational range; a project, group of projects (program), or subproject; a maximum budget or schedule impact. This scope boundary separates decisions that this CCB can make from those that it must escalate to a higher-level CCB or manager for resolution.
l Membership
List the members of this CCB. The CCB typically includes representatives from program management, project management, software engineering, hardware engineering, testing, documentation, customer support, and marketing. One individual is designated as the CCB Chair. Keep the CCB as small as possible, to facilitate its ability to make rapid decisions, but make sure that the critical perspectives are represented.
l Operating Procedures
State the frequency of regularly scheduled CCB meetings and the conditions that will trigger a special meeting. Describe how meetings will be conducted, the number of CCB members who constitute a quorum to make decisions at a meeting, and the roles that must be represented for the meeting to proceed. Identify whether guest participants may attend, such as the individuals who proposed the change requests being considered at a specific meeting.
l Decision-make Process
Describe how the CCB will make its decisions. Indicate whether voting, consensus, unanimity, delegation to a specific individual, or some other decision rule is used to make decisions. State whether the CCB Chair or another manager is permitted to overrule the CCB’s collective decision.
l Communicating Status
Describe how each decision that the CCB makes will be communicated to the individual who requested the change, senior management, project management, affected team members who must implement the change, higher- or lower-level CCBs, and any other stakeholders. Indicate where the decisions and any supporting information, rationale, or data will be stored.
l Scope of authority
Indicate the scope of decisions that the CCB makes. This scope could be over a specific organizational range; a project, group of projects (program), or subproject; a maximum budget or schedule impact. This scope boundary separates decisions that this CCB can make from those that it must escalate to a higher-level CCB or manager for resolution.
l Membership
List the members of this CCB. The CCB typically includes representatives from program management, project management, software engineering, hardware engineering, testing, documentation, customer support, and marketing. One individual is designated as the CCB Chair. Keep the CCB as small as possible, to facilitate its ability to make rapid decisions, but make sure that the critical perspectives are represented.
l Operating Procedures
State the frequency of regularly scheduled CCB meetings and the conditions that will trigger a special meeting. Describe how meetings will be conducted, the number of CCB members who constitute a quorum to make decisions at a meeting, and the roles that must be represented for the meeting to proceed. Identify whether guest participants may attend, such as the individuals who proposed the change requests being considered at a specific meeting.
l Decision-make Process
Describe how the CCB will make its decisions. Indicate whether voting, consensus, unanimity, delegation to a specific individual, or some other decision rule is used to make decisions. State whether the CCB Chair or another manager is permitted to overrule the CCB’s collective decision.
l Communicating Status
Describe how each decision that the CCB makes will be communicated to the individual who requested the change, senior management, project management, affected team members who must implement the change, higher- or lower-level CCBs, and any other stakeholders. Indicate where the decisions and any supporting information, rationale, or data will be stored.
相关文章推荐
- 也谈配置管理团队的建设
- 也谈配置管理团队的建设
- 统一配置管理平台建设
- 配置管理漫漫谈之配置管理组织的建设
- 配置管理漫漫谈之CCB
- 配置管理建设的一点体会
- 通过Cache机制实现通用的配置管理模块
- gVim 配置方案 采用Vundle管理插件(2017更新版)
- Spring声明式事务配置管理方法
- Cisco-C2960交换机管理ip配置
- 利用Spring的AOP来配置和管理你的二级缓存(EHCache)
- DHCP/DNS服务器配置与管理——3
- s5pv210--clocks管理,锁相环和分频器的作用和用法配置
- spring的事物管理配置
- Node版本管理工具NVM配置
- C#配置文件管理
- Dotcms中文教程之一:管理(1.2、修改DotCMS配置属性)
- 第16章 Web服务器配置和管理
- Spring整合Hibernate管理事务(xml配置方式)