|
|||||||
| | 首页 | 工程师论坛 | 下载中心 | 文章中心 | 工程图片 | 工程管理 | 执业资格 | 工程新闻 | 用户留言 | 服务中心 | | |||||||
| 您现在的位置: 工程师之家欢迎您! >> 工程管理 >> 工程管理体系 >> 综合管理 >> 正文 | 用户登录 新用户注册 |
|
|||||
| 项目管理体系中英文对照 | |||||
| 作者:佚名 管理来源:本站原创 点击数: 更新时间:2005-2-7 | |||||
|
一、项目综合管理 Project Integration Management includes the processes required to ensure that the various elements of the project are properly coordinated. It involves making trade-offs among competing objectives and alternatives in order to meet or exceed stakeholder needs and expectations. While all project management processes are integrative to some extent, the processes described in this chapter are primarily integrative. Figure 4-1 provides an overview of the following major processes: These processes interact with each other and with the processes in the other knowledge areas as well. Each process may involve effort from one or more individuals or groups of individuals based on the needs of the project. Each process generally occurs at least once in every project phase. Although the processes are presented here as discrete elements with well-defined interfaces, in practice they may overlap and interact in ways not detailed here. Process interactions are discussed in detail in Chapter 3. The processes, tools, and techniques used to integrate project management processes are the focus of this chapter. For example, project integration management comes into play when a cost estimate is needed for a contingency plan or when risks associated with various staffing alternatives must be identified. However, for a project to be completed successfully, integration must also occur in a number of other areas as well. For example: 项目工作必须同执行组织的连续业务集成。 产品范围和项目范围必须集成(两者区别见第5章-介绍)。 来自不同专业的可交付成果(例如一个工程设计项目的土木、电子和机械绘图)必须集成。 二、项目范围管理 Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. It is primarily concerned with defining and controlling what is or is not included in the project. Figure 5-1 provides an overview of the major project scope management processes: These processes interact with each other and with the processes in the other knowledge areas as well. Each process may involve effort from one or more individuals or groups of individuals based on the needs of the project. Each process generally occurs at least once in every project phase. Although the processes are presented here as discrete elements with well-defined interfaces, in practice they may overlap and interact in ways not detailed here. Process interactions are discussed in detail in Chapter 3. In the project context, the term “scope” may refer to: 产品范围-产品或服务中包含的特征和功能。 项目范围-为了交付具有特定特征和功能的产品所必须做的工作。 The processes, tools and techniques used to manage project scope are the focus of this chapter. The processes, tools and techniques used to manage product scope vary by application area and are usually defined as part of the project life cycle (the project life cycle is discussed in Section 2.1). A project consists of a single product, but that product may include subsidiary elements, each with their own separate but interdependent product scope. For example, a new telephone system would generally include four subsidiary elements—hardware, software, training and implementation. Completion of the product scope is measured against the requirements while completion of the project scope is measured against the plan. Both types of scope management must be well integrated to ensure that the work of the project will result in delivery of the specified product. 三、项目时间管理Project Time Management includes the processes required to ensure timely completion of the project. Figure 6-1 provides an overview of the following major processes: These processes interact with each other and with the processes in the other knowledge areas as well. Each process may involve effort from one or more individuals or groups of individuals based on the needs of the project. Each process generally occurs at least once in every project phase. Although the processes are presented here as discrete elements with well-defined interfaces, in practice they may overlap and interact in ways not detailed here. Process interactions are discussed in detail in Chapter 3. On some projects, especially smaller ones, activity sequencing, activity dueation estimating, and schedule development are so tightly linked that they are viewed as a single process (e.g., they may be performed by a single individual over a relatively short period of time). They are presented here as distinct processes because the tools and techniques for each are different. At present, there is no consensus within the project management profession about the relationship between activities and tasks: 许多应用领域中,工序看成由任务组成。这是比较通用的用法也是推荐的用法。 在其它领域,任务看成由工序组成。 However, the important consideration is not the term used, but whether or not the work to be done is described accurately and understood by those who must do the work. 四、项目质量管理Project Quality Management includes the processes required to ensure that the project will satisfy the needs for which it was undertaken. It includes “all activities of the overall management function that determine the quality policy, objectives, and responsibilities and implements them by means such as quality planning, quality control, quality assurance, and quality improvement, within the quality system”. Figure 8-l provides an overview of the following major project quality management processes: These processes interact with each other and with the processes in the other knowledge areas as well. Each process may involve effort from one or more individuals or groups of individuals based on the needs of the project. Each process generally occurs at least once in every project phase. Although the processes are presented here as discrete elements with well-defined interfaces, in practice they may overlap and interact in ways not detailed here. Process interactions are discussed 1n detail in Chapter 3, Project Management Processes. The basic approach to quality management described in this section is intended to be compatible with that of the international Organization for Standardization (ISO) as detailed in the ISO 9000 and 10000 series of standards and guidelines. This generalized approach should also be compatible with (a) proprietary approaches to quality management such as those recommended by Deming, Juran, Crosby, and others, and (b) non-proprietary approaches such as Total Quality Management (TQM), Continuous Improvement, and others. Project quality management must address both the management of the project and the product of the project. Failure to meet quality requirements in either dimension can have serious negative consequences for any or all of the project Stakeholders. For example: |
|||||
| 管理录入:engineersky 责任编辑:engineersky | |||||
| 【发表评论】【告诉好友】【打印此文】【关闭窗口】 | |||||
| (只显示最新10条。评论内容只代表网友观点,与本站立场无关!) | |
| | 设为首页 | 加入收藏 | 联系站长 | 友情链接 | 版权申明 | | |
![]() |
工程师之家 站长:Zhang Yan |