Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống
1
/ 52 trang
THÔNG TIN TÀI LIỆU
Thông tin cơ bản
Định dạng
Số trang
52
Dung lượng
1,72 MB
Nội dung
Section III TheProjectManagementKnowledge Areas Section III Introduction Chapter 4 Project Integration Management Chapter 5 Project Scope Management Chapter 6 Project Time Management Chapter 7 Project Cost Management Chapter 8 Project Quality Management Chapter 9 Project Human Resource Management Chapter 10 Project Communications Management Chapter 11 Project Risk Management Chapter 12 Project Procurement ManagementAGuidetotheProjectManagementBodyofKnowledge (PMBOK ® Guide) Third Edition 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA 73 S ECTION III Introduction Process Flow Diagrams A process flow diagram is provided in each Knowledge Area chapter (Chapters 4 through 12). The process flow diagram is a summary level depiction ofthe process inputs and process outputs that flow down through all the processes within a specific Knowledge Area. Although the processes are presented here as discrete elements with well-defined interfaces, in practice they are iterative and can overlap and interact in ways not detailed here. Figure III-1. Process Flow Diagram Legend Section III − Introduction AGuidetotheProjectManagementBodyofKnowledge (PMBOK ® Guide) Third Edition 74 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA The symbols for the process flow diagrams are explained in Figure III-1 and depict three types of information: 1. Knowledge Area processes, their interaction with other processes within theKnowledge Area, and their outputs to Chapter 4 integration processes. 2. Processes external totheKnowledge Area, whose outputs are used as inputs totheKnowledge Area processes under discussion. 3. Organizational process assets and enterprise environmental factors are shown as inputs tothe first process. Theprojectmanagement plan, and its subsidiary plans and components that are external totheKnowledge Area, are provided as input into the first process ofthe diagram, and are considered to be available in each subsequent process in their latest updated form. The organizational process assets and enterprise environmental factors are shown as inputs tothe first process to provide those items of information, policy, and procedure that are external tothe project, but can impact theproject planning and execution. These assets and factors, plus the external process outputs used as an input toaKnowledge Area process, are also considered to be available in each subsequent process in their latest updated form. The process flow diagram is not detailed and does not show all the possible interfaces with all external processes. It also does not show possible alternate process flow paths or feedback loops among the specific Knowledge Area processes or with processes external totheKnowledge Area. The iterative nature of most projects makes the permutations ofthe process flows and feedback loops very complex. Therefore, in the interest of keeping the flow diagrams easier to follow, alternate or iterative paths were not included with the diagrams. AGuidetotheProjectManagementBodyofKnowledge (PMBOK ® Guide) Third Edition 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA 75 Figure III-2. Three Major Project Documents and their Relationship to their Components Section III − Introduction AGuidetotheProjectManagementBodyofKnowledge (PMBOK ® Guide) Third Edition 76 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA Major Project Documents There are three major documents described within the PMBOK ® Guide and each has a specific purpose: • Project Charter. Formally authorizes the project. • Project Scope Statement. States what work is to be accomplished and what deliverables need to be produced. • ProjectManagement Plan. States how the work will be performed. Figure III-2 depicts these three documents and their relationship to their components. Theprojectmanagement plan is composed ofthe plans and documents generated by the various processes. Those items are the subsidiary plans and components oftheprojectmanagement plan. AGuidetotheProjectManagementBodyofKnowledge (PMBOK ® Guide) Third Edition 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA 77 4 C HAPTER 4 Project Integration ManagementTheProject Integration ManagementKnowledge Area includes the processes and activities needed to identify, define, combine, unify, and coordinate the various processes and projectmanagement activities within theProjectManagement Process Groups. In theprojectmanagement context, integration includes characteristics of unification, consolidation, articulation, and integrative actions that are crucial toproject completion, successfully meeting customer and other stakeholder requirements, and managing expectations. Integration, in the context of managing a project, is making choices about where to concentrate resources and effort on any given day, anticipating potential issues, dealing with these issues before they become critical, and coordinating work for the overall project good. The integration effort also involves making trade-offs among competing objectives and alternatives. Theprojectmanagement processes are usually presented as discrete components with well-defined interfaces while, in practice, they overlap and interact in ways that cannot be completely detailed in the PMBOK® Guide. The need for integration in projectmanagement becomes evident in situations where individual processes interact. For example, a cost estimate needed for a contingency plan involves integration ofthe planning processes described in greater detail in theProject Cost Management processes, Project Time Management processes, and Project Risk Management processes. When additional risks associated with various staffing alternatives are identified, then one or more of those processes must be revisited. Theproject deliverables also need to be integrated with ongoing operations of either the performing organization or the customer’s organization, or with the long-term strategic planning that takes future problems and opportunities into consideration. Most experienced projectmanagement practitioners know there is no single way to manage a project. They apply projectmanagement knowledge, skills, and processes in different orders and degrees of rigor to achieve the desired project performance. However, the perception that a particular process is not required does not mean that it should not be addressed. Theproject manager and project team must address every process, and the level of implementation for each process must be determined for each specific project. Chapter 4 − Project Integration ManagementAGuidetotheProjectManagementBodyofKnowledge (PMBOK ® Guide) Third Edition 78 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA The integrative nature of projects and projectmanagement can be better understood if we think ofthe other activities performed while completing a project. For example, some activities performed by theprojectmanagement team could be to: • Analyze and understand the scope. This includes theproject and product requirements, criteria, assumptions, constraints, and other influences related toa project, and how each will be managed or addressed within the project. • Document specific criteria ofthe product requirements. • Understand how to take the identified information and transform it into aprojectmanagement plan using the Planning Process Group described in the PMBOK ® Guide. • Prepare the work breakdown structure. • Take appropriate action to have theproject performed in accordance with theprojectmanagement plan, the planned set of integrated processes, and the planned scope. • Measure and monitor project status, processes and products. • Analyze project risks. Among the processes in theProjectManagement Process Groups, the links are often iterated. The Planning Process Group provides the Executing Process Group with a documented projectmanagement plan early in theproject and then facilitates updates totheprojectmanagement plan if changes occur as theproject progresses. Integration is primarily concerned with effectively integrating the processes among theProjectManagement Process Groups that are required to accomplish project objectives within an organization’s defined procedures. Figure 4-1 provides an overview ofthe major projectmanagement integrative processes. Figure 4-2 provides a process flow diagram of those processes and their inputs, outputs and other related Knowledge Area processes. The integrative projectmanagement processes include: 4.1 Develop Project Charter – developing theproject charter that formally authorizes aproject or aproject phase. 4.2 Develop Preliminary Project Scope Statement – developing the preliminary project scope statement that provides a high-level scope narrative. 4.3 Develop ProjectManagement Plan – documenting the actions necessary to define, prepare, integrate, and coordinate all subsidiary plans into aprojectmanagement plan. 4.4 Direct and Manage Project Execution – executing the work defined in theprojectmanagement plan to achieve the project’s requirements defined in theproject scope statement. 4.5 Monitor and Control Project Work – monitoring and controlling the processes used to initiate, plan, execute, and close aprojectto meet the performance objectives defined in theprojectmanagement plan. AGuidetotheProjectManagementBodyofKnowledge (PMBOK ® Guide) Third Edition 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA 79 4 4.6 Integrated Change Control – reviewing all change requests, approving changes, and controlling changes tothe deliverables and organizational process assets. 4.7 Close Project – finalizing all activities across all oftheProjectManagement Process Groups to formally close theproject or aproject phase. Figure 4-1. Project Integration Management Overview Chapter 4 − Project Integration ManagementAGuidetotheProjectManagementBodyofKnowledge (PMBOK ® Guide) Third Edition 80 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA Note: Not all process interactions and data flow among the processes are shown. Figure 4-2. Project Integration Management Processes Flow Diagram [...]... 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 190 73- 3299 USA 85 Chapter 4 − Project Integration Management3ProjectManagement Information System TheProjectManagement Information System (PMIS) is a standardized set of automated tools available within the organization and integrated into a system The PMIS is used by theprojectmanagement team to support generation of a. .. 1 ProjectManagement Methodology Theprojectmanagement methodology defines a process, which aids aprojectmanagement team in developing and controlling changes totheprojectmanagement plan .2 ProjectManagement Information System Theprojectmanagement information system, an automated system, is used by theprojectmanagement team to support generation oftheprojectmanagement plan, facilitate... Develop Project Charter Theproject charter is the document that formally authorizes aprojectTheproject charter provides theproject manager with the authority to apply organizational resources toproject activities Aproject manager is identified and assigned as early in theproject as is feasible Theproject manager should always be assigned prior tothe start of planning, and preferably while the project. .. consolidated and combined into a functioning unified whole Aprojectmanagement methodology may or may not be an elaboration ofaprojectmanagement standard Aprojectmanagement methodology can be either a formal mature process or an informal technique that aids aprojectmanagement team in effectively developing aproject charter ® A Guide totheProjectManagement Body ofKnowledge (PMBOK Guide) ... theprojectmanagement plan .2 ProjectManagement Information System Theprojectmanagement information system (PMIS), an automated system, is used by theprojectmanagement team to monitor and control the execution of activities that are planned and scheduled in the projectmanagement plan The PMIS is also used to create new forecasts as needed .3 Earned Value Technique The earned value technique measures... ProjectManagement Information System Theprojectmanagement information system, an automated system, is used by theprojectmanagement team to support generation ofa preliminary project scope statement, facilitate feedback as the document is refined, control changes totheproject scope statement, and release the approved document .3 Expert Judgment Expert judgment is applied to any technical and management. .. as a scheduling software tool, a configuration management system, an information collection and distribution system, or web interfaces to other online automated systems) ® A Guide totheProjectManagement Body ofKnowledge (PMBOK Guide) Third Edition 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 190 73- 3299 USA 83 Chapter 4 − Project Integration Management 4 Organizational... Methodology Theprojectmanagement methodology defines a process that aids aprojectmanagement team in developing and controlling changes tothe preliminary project scope statement ® A Guide totheProjectManagement Body ofKnowledge (PMBOK Guide) Third Edition 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 190 73- 3299 USA 87 Chapter 4 − Project Integration Management 2 Project. .. plan ® 90 A Guide totheProjectManagement Body ofKnowledge (PMBOK Guide) Third Edition 2004 ProjectManagement Institute, Four Campus Boulevard, Newtown Square, PA 190 73- 3299 USA 4 .3. 3 Develop ProjectManagement Plan: Outputs 1 4.4 ProjectManagement Plan Described in the introduction to Section 4 .3 Direct and Manage Project Execution The Direct and Manage Project Execution process requires the project. .. 4 ProjectManagement Information System Theprojectmanagement information system is an automated system used by theprojectmanagement team to aid execution ofthe activities planned in theprojectmanagement plan 4.4 .3 Direct and Manage Project Execution: Outputs 1 Deliverables A deliverable is any unique and verifiable product, result or capability to perform a service that is identified in theproject . Communications Management Chapter 11 Project Risk Management Chapter 12 Project Procurement Management A Guide to the Project Management Body of Knowledge. an elaboration of a project management standard. A project management methodology can be either a formal mature process or an informal technique that aids