維基百科

使用者:VKeksburg/沙盒/專案管理

< User:VKeksburg | 沙盒

專案管理是領導一個團隊在規定時間內實現目標和達到成功標準的過程,其主要挑戰在於在給定的約束條件下實現所有專案目標[1]，在社會科學領域是管理學的一個分支學科。這些信息通常包含於在開發過程初期建立的專案文檔中。主要的約束條件是範圍、時間、預算[2]其次是優化資源配置的必要投入，並將其應用於實現既定目標。

專案管理的目的是產生一個符合客戶目標的完整專案，在許多情景下也可以通過塑造或改變客戶的想法，更切實地實現客戶的目標。一旦明確了客戶的目標，就應該讓目標指導參與專案的其他人員——例如專案經理、設計師、承包商和分包商等——做出的所有決策。定義不清或規定過嚴的專案管理目標不利於良好決策。

專案具有臨時性，目的在於生產一種獨特的產品、服務或結果，具有明確的開始和結束，通常還受到時間、資金和人員限制。[3][4]專案的臨時性與商業中的「一切照舊」（即business as usual）[5] 形成對比，後者是為生產產品或服務而進行的重複的、永久或半永久的實踐活動。

歷史

在20世紀之前，土木工程等一般都是由負責專案的建築師、工程師等自行管理，例如維特魯威（公元前一世紀）、克里斯多佛·雷恩（1632-1723）、托馬斯·特爾福德（1757-1834）和伊桑巴德·金德姆·布魯內爾（1806-1859）。[6]從20世紀50年代起，人們開始系統地將專案管理的工具和技術應用於複雜的工程專案。[7]

 
亨利·甘特（1861–1919），規劃和控制技術之父

作為一門學科，專案管理是從土木工程、建築和國防等幾個應用領域發展而來。[8]專案管理的兩位奠基者是因甘特圖而聞名的「計劃和控制技術之父」亨利·甘特，[9]與創立了按職能劃分的古典管理理論的亨利·法約爾，[10]而二位都繼承了泰勒的科學管理理論。

20世紀50年代標誌著現代專案管理的開始，主要特徵是核心工程領域聚集在一起作為一個整體工作。專案管理成為公認的從管理學科中產生的一門具有工程模式的獨特學科。[11]在美國，20世紀50年代以前，專案管理是臨時的，主要使用甘特圖和非正規的技術工具，例如關鍵路徑法和計劃評審技術兩種數學專案調度模型。關鍵路徑法（CPM）是杜邦公司和雷明頓蘭德公司聯合開發的，用於管理工廠維護專案。「計劃評審技術」（PERT），是由美國海軍與洛克希德公司和博思艾倫諮詢公司作為研發「北極星」號潛艇飛彈系統的一部分聯合開發的。[12]

PERT和CPM在方法上非常相似，但仍存在一些差異。CPM用於假設確定活動時間的專案；每項活動進行的時間是已知的。另一方面，PERT允許隨機的活動時間；每個活動進行的時間是不確定的或變化的。由於這一核心區別，CPM和PERT被用於不同的場合。這些數學技術迅速普及到很多民營企業。

 
一個7個月的專案，5個裡程碑的PERT網絡圖

與此同時，隨著專案調度模型的完善，專案成本估算、成本管理和工程經濟的技術也在不斷發展。1956年，美國造價工程師協會主要由專案管理和相關的規劃調度、成本估算控制等的從業人員組成。這一協會繼續其開創性的工作，並在2006年發布了第一個投資組合、計劃和專案管理的綜合流程（即總成本管理框架）。

1969年，國際專案管理學會在美國成立。[13]這一學會於1996年出版了以威廉·鄧肯主編的《專案管理知識體系指南》的原始版本，該指南描述了 "大多數專案、大多數時間 "所共有的專案管理實踐。

類型

專案管理方法適用於一切專案。它通常根據專案規模，性質，行業或部門針對特定類型的專案量身定製成專門的專案管理形式，例如建築專案管理專務於道路橋梁等的建設[14]，IT專案管理關注技術資產和服務以及軟體生命周期，生物技術專案管理關注複雜的生物技術研發。[15]本地化專案管理把許多專案管理的方法應用在文字翻譯工作中，別具一格。公共專案管理涵蓋了政府的所有公共工程，可以由政府機構執行或外包給承包商。專案管理還可以基於硬或軟（即物理或非物理）進行分類。

各種專案管理的共通點在於以下三個重要目標：時間，品質和預算。成功的專案將按計劃，在預算範圍內並根據先前商定的品質標準完成，即達到鐵三角或三重約束條件，這是評判專案成敗的重要依據。[16]

專案經理會總結製作在該行業進行專案管理的可重複模板，以此明晰透徹，減少重複性工作，具有提高品質，降低成本和縮短時間的效果。

方法

2017年的一項研究表明，專案成功都取決於影響專案的四個關鍵方面，即4P：[17]

  • 計劃：計劃和預測活動；
  • 流程： 專案所有活動的全過程；
  • 人員：人員安排及其協作交流；
  • 權力： 權限範圍，決策者，組織結構，策略實施等。

有多種方法可以組織和完成專案活動，包括分階段，精益，迭代和增量等。專案計劃也有一些擴展，例如基於產品的結果或基於過程的活動。

無論方法論如何，都必須仔細考慮整個專案的目標，時間表和成本，以及所有參與者和利益相關者的角色和責任。[18]

效益實現管理

主條目：Benefits realisation management

Benefits realization management (BRM) enhances normal project management techniques through a focus on outcomes (benefits) of a project rather than products or outputs, and then measuring the degree to which that is happening to keep a project on track. This can help to reduce the risk of a completed project being a failure by delivering agreed upon requirements (outputs) i.e. project success but failing to deliver the benefits (outcomes) of those requirements i.e. product success.

In addition, BRM practices aim to ensure the strategic alignment between project outcomes and business strategies. The effectiveness of these practices is supported by recent research evidencing BRM practices influencing project success from a strategic perspective across different countries and industries. These wider effects are called the strategic impact.[19]

An example of delivering a project to requirements might be agreeing to deliver a computer system that will process staff data and manage payroll, holiday and staff personnel records in shorter times with reduced errors. Under BRM, the agreement might be to achieve a specified reduction in staff hours and errors required to process and maintain staff data after the system installation when compared with without the system.

關鍵鏈專案管理

主條目：Critical chain project management

Critical chain project management (CCPM) is an application of the theory of constraints (TOC) to planning and managing projects, and is designed to deal with the uncertainties inherent in managing projects, while taking into consideration limited availability of resources (physical, human skills, as well as management & support capacity) needed to execute projects.

The goal is to increase the flow of projects in an organization (throughput). Applying the first three of the five focusing steps of TOC, the system constraint for all projects, as well as the resources, are identified. To exploit the constraint, tasks on the critical chain are given priority over all other activities. Finally, projects are planned and managed to ensure that the resources are ready when the critical chain tasks must start, subordinating all other resources to the critical chain.

掙值管理

主條目：Earned value management

Earned value management (EVM) extends project management with techniques to improve project monitoring. It illustrates project progress towards completion in terms of work and value (cost). Earned Schedule is an extension to the theory and practice of EVM.

迭代式專案管理

參見：迭代式開發

In critical studies of project management, it has been noted that phased approaches are not well suited for projects which are large-scale and multi-company,[20] with undefined, ambiguous, or fast-changing requirements,[21] or those with high degrees of risk, dependency, and fast-changing technologies.[22] The cone of uncertainty explains some of this as the planning made on the initial phase of the project suffers from a high degree of uncertainty. This becomes especially true as software development is often the realization of a new or novel product.

These complexities are better handled with a more exploratory or iterative and incremental approach.[23] Several models of iterative and incremental project management have evolved, including agile project management, dynamic systems development method, extreme project management, and Innovation Engineering®.[24]

精益專案管理

主條目：Lean project management

Lean project management uses the principles from lean manufacturing to focus on delivering value with less waste and reduced time.

Phased approach

The phased (or staged) approach breaks down and manages the work through a series of distinct steps to be completed, and is often referred to as "traditional"[25] or "waterfall".[26] Although it can vary, it typically consists of five process areas, four phases plus control:

 
Typical development phases of an engineering project
  1. initiation.
  2. planning and design.
  3. construction.
  4. monitoring and controlling.
  5. completion or closing.

Many industries use variations of these project stages and it is not uncommon for the stages to be renamed to better suit the organization. For example, when working on a brick-and-mortar design and construction, projects will typically progress through stages like pre-planning, conceptual design, schematic design, design development, construction drawings (or contract documents), and construction administration.

While the phased approach works well for small, well-defined projects, it often results in challenge or failure on larger projects, or those that are more complex or have more ambiguities, issues and risk.[27]

基於流程的管理

主條目：Process-based management

The incorporation of process-based management has been driven by the use of maturity models such as the OPM3 and the CMMI (capability maturity model integration; see this example of a predecessor) and ISO/IEC 15504 (SPICE – software process improvement and capability estimation). Unlike SEI's CMM, the OPM3 maturity model describes how to make project management processes capable of performing successfully, consistently, and predictably to enact the strategies of an organization.

專案生產管理

主條目：Project production management

Project production management is the application of operations management to the delivery of capital projects. The Project production management framework is based on a project as a production system view, in which a project transforms inputs (raw materials, information, labor, plant & machinery) into outputs (goods and services).[28]

基於產品的計劃

主條目：Product-based planning

Product-based planning is a structured approach to project management, based on identifying all of the products (project deliverables) that contribute to achieving the project objectives. As such, it defines a successful project as output-oriented rather than activity- or task-oriented.[29] The most common implementation of this approach is PRINCE2.[30]

Process groups

 
The project development stages[31]

Traditionally (depending on what project management methodology is being used), project management includes a number of elements: four to five project management process groups, and a control system. Regardless of the methodology or terminology used, the same basic project management processes or stages of development will be used. Major process groups generally include:[32]

  • Initiation
  • Planning
  • Production or execution
  • Monitoring and controlling
  • Closing

In project environments with a significant exploratory element (e.g., research and development), these stages may be supplemented with decision points (go/no go decisions) at which the project's continuation is debated and decided. An example is the Phase–gate model.

Initiating

 
Initiating process group processes[31]

The initiating processes determine the nature and scope of the project.[33] If this stage is not performed well, it is unlikely that the project will be successful in meeting the business』 needs. The key project controls needed here are an understanding of the business environment and making sure that all necessary controls are incorporated into the project. Any deficiencies should be reported and a recommendation should be made to fix them.

The initiating stage should include a plan that encompasses the following areas. These areas can be recorded in a series of documents called Project Initiation documents. Project Initiation documents are a series of planned documents used to create order for the duration of the project. These tend to include:

計劃

After the initiation stage, the project is planned to an appropriate level of detail (see example of a flow-chart).[31] The main purpose is to plan time, cost, and resources adequately to estimate the work needed and to effectively manage risk during project execution. As with the Initiation process group, a failure to adequately plan greatly reduces the project's chances of successfully accomplishing its goals.

Project planning generally consists of[34]

  • determining the project management methodology to follow (e.g. whether the plan will be defined wholly up front, iteratively, or in rolling waves);
  • developing the scope statement;
  • selecting the planning team;
  • identifying deliverables and creating the product and work breakdown structures;
  • identifying the activities needed to complete those deliverables and networking the activities in their logical sequence;
  • estimating the resource requirements for the activities;
  • estimating time and cost for activities;
  • developing the schedule;
  • developing the budget;
  • risk planning;
  • developing quality assurance measures;
  • gaining formal approval to begin work.

Additional processes, such as planning for communications and for scope management, identifying roles and responsibilities, determining what to purchase for the project and holding a kick-off meeting are also generally advisable.

For new product development projects, conceptual design of the operation of the final product may be performed concurrent with the project planning activities, and may help to inform the planning team when identifying deliverables and planning activities.

執行

 
Executing process group processes[31]

While executing we must know what are the planned terms that need to be executed. The execution/implementation phase ensures that the project management plan's deliverables are executed accordingly. This phase involves proper allocation, co-ordination and management of human resources and any other resources such as material and budgets. The output of this phase is the project deliverables.

專案文件

Documenting everything within a project is key to being successful. To maintain budget, scope, effectiveness and pace a project must have physical documents pertaining to each specific task. With correct documentation, it is easy to see whether or not a project's requirement has been met. To go along with that, documentation provides information regarding what has already been completed for that project. Documentation throughout a project provides a paper trail for anyone who needs to go back and reference the work in the past. In most cases, documentation is the most successful way to monitor and control the specific phases of a project. With the correct documentation, a project's success can be tracked and observed as the project goes on. If performed correctly documentation can be the backbone to a project's success

監測控制

 
Monitoring and controlling process group processes[31]

Monitoring and controlling consists of those processes performed to observe project execution so that potential problems can be identified in a timely manner and corrective action can be taken, when necessary, to control the execution of the project. The key benefit is that project performance is observed and measured regularly to identify variances from the project management plan.

Monitoring and controlling includes:[35]

  • Measuring the ongoing project activities ('where we are');
  • Monitoring the project variables (cost, effort, scope, etc.) against the project management plan and the project performance baseline (where we should be);
  • Identifying corrective actions to address issues and risks properly (How can we get on track again);
  • Influencing the factors that could circumvent integrated change control so only approved changes are implemented.

Two main mechanisms support monitoring and controlling in projects. On the one hand, contracts offer a set of rules and incentives often supported by potential penalties and sanctions.[36] On the other hand, scholars in business and management have paid attention to the role of integrators (also called project barons) to achieve a project’s objectives.[37][38] In turn, recent research in project management has questioned the type of interplay between contracts and integrators. Some have argued that these two monitoring mechanisms operate as substitutes[39] as one type of organization would decrease the advantages of using the other one, while others have suggested that they can complement each other.[40]

In multi-phase projects, the monitoring and control process also provides feedback between project phases, to implement corrective or preventive actions to bring the project into compliance with the project management plan.

Project maintenance is an ongoing process, and it includes:[32]

  • Continuing support of end-users
  • Correction of errors
  • Updates to the product over time
 
Monitoring and controlling cycle

In this stage, auditors should pay attention to how effectively and quickly user problems are resolved.

Over the course of any construction project, the work scope may change. Change is a normal and expected part of the construction process. Changes can be the result of necessary design modifications, differing site conditions, material availability, contractor-requested changes, value engineering, and impacts from third parties, to name a few. Beyond executing the change in the field, the change normally needs to be documented to show what was actually constructed. This is referred to as change management. Hence, the owner usually requires a final record to show all changes or, more specifically, any change that modifies the tangible portions of the finished work. The record is made on the contract documents – usually, but not necessarily limited to, the design drawings. The end product of this effort is what the industry terms as-built drawings, or more simply, "as built." The requirement for providing them is a norm in construction contracts. Construction document management is a highly important task undertaken with the aid of an online or desktop software system, or maintained through physical documentation. The increasing legality pertaining to the construction industry's maintenance of correct documentation has caused the increase in the need for document management systems.

When changes are introduced to the project, the viability of the project has to be re-assessed. It is important not to lose sight of the initial goals and targets of the projects. When the changes accumulate, the forecasted result may not justify the original proposed investment in the project. Successful project management identifies these components, and tracks and monitors progress, so as to stay within time and budget frames already outlined at the commencement of the project. Exact methods were suggested to identify the most informative monitoring points along the project life-cycle regarding its progress and expected duration.[41]

專案終結

 
Closing process group processes.[31]

Closing includes the formal acceptance of the project and the ending thereof. Administrative activities include the archiving of the files and documenting lessons learned.

This phase consists of:[32]

  • Contract closure: Complete and settle each contract (including the resolution of any open items) and close each contract applicable to the project or project phase.
  • Project close: Finalize all activities across all of the process groups to formally close the project or a project phase

Also included in this phase is the Post Implementation Review. This is a vital phase of the project for the project team to learn from experiences and apply to future projects. Normally a Post Implementation Review consists of looking at things that went well and analyzing things that went badly on the project to come up with lessons learned.

專案控制及其系統

Project controlling (also known as Cost Engineering) should be established as an independent function in project management. It implements verification and controlling function during the processing of a project to reinforce the defined performance and formal goals.[42] The tasks of project controlling are also:

  • the creation of infrastructure for the supply of the right information and its update
  • the establishment of a way to communicate disparities of project parameters
  • the development of project information technology based on an intranet or the determination of a project key performance indicator system (KPI)
  • divergence analyses and generation of proposals for potential project regulations[43]
  • the establishment of methods to accomplish an appropriate project structure, project workflow organization, project control and governance
  • creation of transparency among the project parameters[44]

Fulfillment and implementation of these tasks can be achieved by applying specific methods and instruments of project controlling. The following methods of project controlling can be applied:

  • investment analysis
  • cost–benefit analysis
  • value benefit analysis
  • expert surveys
  • simulation calculations
  • risk-profile analysis
  • surcharge calculations
  • milestone trend analysis
  • cost trend analysis
  • target/actual-comparison[45]

Project control is that element of a project that keeps it on track, on-time and within budget.[35] Project control begins early in the project with planning and ends late in the project with post-implementation review, having a thorough involvement of each step in the process. Projects may be audited or reviewed while the project is in progress. Formal audits are generally risk or compliance-based and management will direct the objectives of the audit. An examination may include a comparison of approved project management processes with how the project is actually being managed.[46] Each project should be assessed for the appropriate level of control needed: too much control is too time-consuming, too little control is very risky. If project control is not implemented correctly, the cost to the business should be clarified in terms of errors and fixes.

Control systems are needed for cost, risk, quality, communication, time, change, procurement, and human resources. In addition, auditors should consider how important the projects are to the financial statements, how reliant the stakeholders are on controls, and how many controls exist. Auditors should review the development process and procedures for how they are implemented. The process of development and the quality of the final product may also be assessed if needed or requested. A business may want the auditing firm to be involved throughout the process to catch problems earlier on so that they can be fixed more easily. An auditor can serve as a controls consultant as part of the development team or as an independent auditor as part of an audit.

Businesses sometimes use formal systems development processes. These help assure systems are developed successfully. A formal process is more effective in creating strong controls, and auditors should review this process to confirm that it is well designed and is followed in practice. A good formal systems development plan outlines:

  • A strategy to align development with the organization's broader objectives
  • Standards for new systems
  • Project management policies for timing and budgeting
  • Procedures describing the process
  • Evaluation of quality of change

專案特點

單個專案有五個重要特點：（1）具體的開始與終結日期；（2）執行與完成專案的主體是人；（3）成果是特定的產品或服務；（4）臨時性；（5）分步驟執行。

專案複雜性

Complexity and its nature plays an important role in the area of project management. Despite having number of debates on this subject matter, studies suggest lack of definition and reasonable understanding of complexity in relation to management of complex projects.[47] As it is considered that project complexity and project performance are closely related, it is important to define and measure complexity of the project for project management to be effective.[48]

By applying the discovery in measuring work complexity described in Requisite Organization and Stratified Systems Theory, Dr Elliott Jaques classifies projects and project work (stages, tasks) into basic 7 levels of project complexity based on such criteria as time-span of discretion and complexity of a project's output:[49][50]

  • Level 1 Project – improve the direct output of an activity (quantity, quality, time) within a business process with targeted completion time up to 3 months.
  • Level 2 Project – develop and improve compliance to a business process with targeted completion time from 3 months to 1 year.
  • Level 3 Project – develop, change, and improve a business process with targeted completion time from 1 to 2 years.
  • Level 4 Project – develop, change, and improve a functional system with targeted completion time from 2 to 5 years.
  • Level 5 Project – develop, change, and improve a group of functional systems / business function with targeted completion time from 5 to 10 years.
  • Level 6 Project – develop, change, and improve a whole single value chain of a company with targeted completion time from 10 to 20 years.
  • Level 7 Project – develop, change, and improve multiple value chains of a company with target completion time from 20 to 50 years.[51]

Benefits from measuring Project Complexity is to improve project people feasibility by:[52]

  • Match the level of a project's complexity with effective targeted completion time of a project
  • Match the level of a project's complexity with the respective capability level of the project manager
  • Match the level of a project task's complexity with the respective capability of the project members

專案管理者

A project manager is a professional in the field of project management. Project managers are in charge of the people in a project. People are the key to any successful project. Without the correct people in the right place and at the right time a project cannot be successful. Project managers can have the responsibility of the planning, execution, controlling, and closing of any project typically relating to the construction industry, engineering, architecture, computing, and telecommunications. Many other fields of production engineering, design engineering, and heavy industrial have project managers.

A project manager needs to understand the order of execution of a project to schedule the project correctly as well as the time necessary to accomplish each individual task within the project. A project manager is the person accountable for accomplishing the stated project objectives on the behalf of the client. Project Managers tend to have multiple years』 experience in their field. A project manager is required to know the project in and out while supervising the workers along with the project. Typically in most construction, engineering, architecture, and industrial projects, a project manager has another manager working alongside of them who is typically responsible for the execution of task on a daily basis. This position in some cases is known as a superintendent. A superintendent and project manager work hand in hand in completing daily project task. Key project management responsibilities include creating clear and attainable project objectives, building the project requirements, and managing the triple constraint (now including more constraints and calling it competing constraints) for projects, which is cost, time, quality and scope for the first three but about three additional ones in current project management. A typical project is composed of a team of workers who work under the project manager to complete the assignment within the time and budget targets. A project manager normally reports directly to someone of higher stature on the completion and success of the project.

A project manager is often a client representative and has to determine and implement the exact needs of the client, based on knowledge of the firm they are representing. The ability to adapt to the various internal procedures of the contracting party, and to form close links with the nominated representatives, is essential in ensuring that the key issues of cost, time, quality and above all, client satisfaction, can be realized.

A complete project manager, a term first coined by Dr. Robert J. Graham in his simulation, has been expanded upon by Randall L. Englund and Alfonso Bucero. They describe a complete project manager as a person who embraces multiple disciplines, such as leadership, influence, negotiations, politics, change and conflict management, and humor. These are all "soft" people skills that enable project leaders to be more effective and achieve optimized, consistent results.

多層次成功框架和標準

There is a tendency to confuse the project success with project management success. They are two different things. Project management success criteria is different from project success criteria. The project management is said to be successful if the given project is completed within the agreed upon time, met the agreed upon scope and within the agreed upon budget. Subsequent to the triple constraints, multiple constraints have been considered to ensure project success. However, the triple or multiple constraints indicate only the efficiency measures of the project, which are indeed the project management success criteria during the project lifecycle.

The priori criteria leave out the more important after-completion results of the project which comprise four levels i.e. the output (product) success, outcome (benefits) success and impact (strategic) success during the product lifecycle. These posterior success criteria indicate the effectiveness measures of the project product, service or result, after the project completion and handover. This overarching multilevel success framework of projects, programs and portfolios has been developed by Paul Bannerman in 2008.[53] In other words, a project is said to be successful, when it succeeds in achieving the expected business case which needs to be clearly identified and defined during the project inception and selection before starting the development phase. This multilevel success framework conforms to the theory of project as a transformation depicted as the input-process / activity-output-outcome-impact in order to generate whatever value intended. Emanuel Camilleri in 2011 classifies all the critical success and failure factors into groups and matches each of them with the multilevel success criteria in order to deliver business value.[54]

風險管理

主條目：Project risk management

The United States Department of Defense states; "Cost, Schedule, Performance, and Risk" are the four elements through which Department of Defense acquisition professionals make trade-offs and track program status.[55] There are also international standards. Risk management applies proactive identification (see tools) of future problems and understanding of their consequences allowing predictive decisions about projects.

工作分解結構

主條目：Work breakdown structure和Scope (project management)

The work breakdown structure (WBS) is a tree structure that shows a subdivision of the activities required to achieve an objective – for example a portfolio, program, project, and contract. The WBS may be hardware-, product-, service-, or process-oriented (see an example in a NASA reporting structure (2001)).[56] Beside WBS for project scope management, there are organizational breakdown structure (chart), cost breakdown structure and risk breakdown structure.

A WBS can be developed by starting with the end objective and successively subdividing it into manageable components in terms of size, duration, and responsibility (e.g., systems, subsystems, components, tasks, sub-tasks, and work packages), which include all steps necessary to achieve the objective.[27]

The work breakdown structure provides a common framework for the natural development of the overall planning and control of a contract and is the basis for dividing work into definable increments from which the statement of work can be developed and technical, schedule, cost, and labor hour reporting can be established.[56] The work breakdown structure can be displayed in two forms, as a table with subdivision of tasks or as an organisational chart whose lowest nodes are referred to as "work packages".

It is an essential element in assessing the quality of a plan, and an initial element used during the planning of the project. For example, a WBS is used when the project is scheduled, so that the use of work packages can be recorded and tracked.

國際標準

There are several project management standards, including:

  • The ISO standards ISO 9000, a family of standards for quality management systems, and the ISO 10006:2003, for Quality management systems and guidelines for quality management in projects.
  • ISO 21500:2012 – Guidance on project management. This is the first International Standard related to project management published by ISO. Other standards in the 21500 family include 21503:2017 Guidance on programme management; 21504:2015 Guidance on portfolio management; 21505:2017 Guidance on governance; 21506:2018 Vocabulary; 21508:2018 Earned value management in project and programme management; and 21511:2018 Work breakdown structures for project and programme management.
  • ISO 31000:2009 – Risk management.
  • ISO/IEC/IEEE 16326:2009 – Systems and Software Engineering—Life Cycle Processes—Project Management[57]
  • Individual Competence Baseline (ICB) from the International Project Management Association (IPMA).[58]
  • Capability Maturity Model (CMM) from the Software Engineering Institute.
  • GAPPS, Global Alliance for Project Performance Standards – an open source standard describing COMPETENCIES for project and program managers.
  • HERMES method, Swiss general project management method, selected for use in Luxembourg and international organizations.
  • The logical framework approach (LFA), which is popular in international development organizations.
  • PMBOK Guide from the Project Management Institute (PMI).
  • PRINCE2 from AXELOS.
  • Team Software Process (TSP) from the Software Engineering Institute.
  • Total Cost Management Framework, AACE International's Methodology for Integrated Portfolio, Program and Project Management.
  • V-Model, an original systems development method.

計劃管理

主條目：Program management

Some projects, either identical or different, can be managed as program management so that a program manager is in charge of project managers. Hence, a program manager is also known as a project director.

專案組合管理

主條目：Project portfolio management

An increasing number of organizations are using what is referred to as project portfolio management (PPM) as a means of selecting the right projects and then using project management techniques[59] as the means for delivering the outcomes in the form of benefits to the performing public, private or not-for-profit organization. PPM is usually performed by a dedicated team of managers organized within an Enterprise Project Management Office (PMO) headed by a PMO director, usually based within the organization. Thus, the position in charge of PPM can also be designated as the chief project officer or the chief technology officer. In cases where strategic initiatives of an organization form the bulk of the PPM, the head of the PPM is titled as the chief initiative officer.

專案管理軟體

主條目：Project management software和Project management information system

Project management software is software used to help plan, organize, and manage resource pools, develop resource estimates and implement plans. Depending on the sophistication of the software, functionality may include estimation and planning, scheduling, cost control and budget management, resource allocation, collaboration software, communication, decision-making, workflow, risk, quality, documentation, and/or administration systems.[60][61]

可視化專案管理

主條目：Virtual team

Virtual program management (VPM) is management of a project done by a virtual team, though it rarely may refer to a project implementing a virtual environment[62] It is noted that managing a virtual project is fundamentally different from managing traditional projects,[63] combining concerns of telecommuting and global collaboration (culture, time zones, language).[64]

See also

參考文獻

  1. ^ (2003). PMP Project Management Professional Study Guide. McGraw-Hill Professional, 2003. ISBN 0-07-223062-2 p.354.
  2. ^ Baratta, Angelo. The triple constraint a triple illusion. PMI. 2006 [22 December 2020]. 
  3. ^ The Definitive Guide to Project Management. Nokes, Sebastian. 2nd Ed.n. London (Financial Times / Prentice Hall): 2007. ISBN 978-0-273-71097-4
  4. ^ What is Project Management?. Project Management Institute. [2014-06-04]. 
  5. ^ Paul C. Dinsmore et al (2005) The right projects done right! John Wiley and Sons, 2005. ISBN 0-7879-7113-8. p.35 and further.
  6. ^ Dennis Lock (2007) Project Management (9th ed.) Gower Publishing, Ltd., 2007. ISBN 0-566-08772-3
  7. ^ Young-Hoon Kwak (2005). "A brief History of Project Management". In: The story of managing projects. Elias G. Carayannis et al. (9 eds), Greenwood Publishing Group, 2005. ISBN 1-56720-506-2
  8. ^ David I. Cleland, Roland Gareis (2006). Global Project Management Handbook. "Chapter 1: "The evolution of project management". McGraw-Hill Professional, 2006. ISBN 0-07-146045-4
  9. ^ Martin Stevens (2002). Project Management Pathways. Association for Project Management. APM Publishing Limited, 2002 ISBN 1-903494-01-X p.xxii
  10. ^ Morgen Witzel (2003). Fifty key figures in management. Routledge, 2003. ISBN 0-415-36977-0. p. 96-101.
  11. ^ David I. Cleland, Roland Gareis (2006). Global Project Management Handbook. McGraw-Hill Professional, 2006. ISBN 0-07-146045-4. p.1-4 states: "It was in the 1950s when project management was formally recognized as a distinct contribution arising from the management discipline."
  12. ^ Malcolm, D. G., Roseboom, J. H., Clark, C. E., & Fazar, W. (1959). "Application of a technique for research and development program evaluation." Operations research, 7(5), 646-669.
  13. ^ F. L. Harrison, Dennis Lock (2004). Advanced project management: a structured approach. Gower Publishing, Ltd., 2004. ISBN 0-566-07822-8. p.34.
  14. ^ Certified Construction Manager. CMAA. [23 November 2013]. 
  15. ^ Certificate in Biotechnology Project Management. University of Washington. [23 November 2013]. 
  16. ^ Esselink, Bert. A Practical Guide to Localization. Amsterdam/Philadelphia: John Benjamins Publishing Company. 2000: 428. ISBN 978-9-027-21956-5. 
  17. ^ Mesly, Olivier. (2017). Project feasibility – Tools for uncovering points of vulnerability. New York, NY: Taylor and Francis, CRC Press. 546 pages. ISBN 9 781498 757911.
  18. ^ Cf. The Bridger (blog), "Project management: PMP, Prince 2, or an Iterative or Agile variant"
  19. ^ Serra, C. E. M.; Kunc, M. Benefits Realisation Management and its influence on project success and on the execution of business strategies. International Journal of Project Management. 2014, 33 (1): 53–66. doi:10.1016/j.ijproman.2014.03.011  . 
  20. ^ Hass, Kathleen B. (Kitty). Managing Complex Projects that are Too Large, Too Long and Too Costly. PM Times. March 2, 2010 [2017-06-27] （英國英語）. 
  21. ^ Conforto, E. C.; Salum, F.; Amaral, D. C.; da Silva, S. L.; Magnanini de Almeida, L. F. Can agile project management be adopted by industries other than software development?. Project Management Journal. June 2014, 45 (3): 21–34. S2CID 110595660. doi:10.1002/pmj.21410. 
  22. ^ Patel, Himanshu. The Waterfall Model In Project Management Explained. ItsGuru. April 20, 2018 [2017-04-20] （英國英語）. 
  23. ^ Snowden, David J.; Boone, Mary E. A Leader's Framework for Decision Making. Harvard Business Review. November 2007 [2017-06-27]. 
  24. ^ Stanford Research Study Finds Innovation Engineering is a true "Breakout Innovation" System. IE News. June 20, 2017 [2017-08-11] （英國英語）. 
  25. ^ Wysocki, Robert K. Effective Project Management: Traditional, Adaptive, Extreme Seventh. John Wiley & Sons. 2013. ISBN 978-1118729168. 
  26. ^ Winston W. Royce (1970). "Managing the Development of Large Software Systems" 網際網路檔案館的存檔，存檔日期2016-03-15. in: Technical Papers of Western Electronic Show and Convention (WesCon) August 25–28, 1970, Los Angeles, USA.
  27. ^ 27.0 27.1 Stellman, Andrew; Greene, Jennifer. Applied Software Project Management. O'Reilly Media. 2005. ISBN 978-0-596-00948-9. （原始內容存檔於2015-02-09）. 
  28. ^ McCaffer, Ronald; Harris, Frank. Modern construction management. Wiley-Blackwell. 2013: 5. ISBN 978-1118510186. OCLC 834624541. 
  29. ^ Office for Government Commerce (1996) Managing Successful Projects with PRINCE2, p14
  30. ^ OGC – PRINCE2 – Background
  31. ^ 31.0 31.1 31.2 31.3 31.4 31.5 Project Management Guide (PDF). VA Office of Information and Technology. 2003. 原始內容存檔於January 14, 2009. 
  32. ^ 32.0 32.1 32.2 PMI (2010). A Guide to the Project Management Body of Knowledge p.27-35
  33. ^ Peter Nathan, Gerald Everett Jones (2003). PMP certification for dummies. p.63.
  34. ^ Harold Kerzner. Project Management: A Systems Approach to Planning, Scheduling, and Controlling  8th. Wiley. 2003. ISBN 0-471-22577-0. 
  35. ^ 35.0 35.1 James P. Lewis (2000). The project manager's desk reference: : a comprehensive guide to project planning, scheduling, evaluation, and systems. p.185
  36. ^ Eccles, Robert G. The quasifirm in the construction industry. Journal of Economic Behavior & Organization. 1981, 2 (4): 335–357. ISSN 0167-2681. doi:10.1016/0167-2681(81)90013-5. 
  37. ^ Davies, Andrew; Hobday, Michael. The Business of projects: managing innovation in complex products and systems. Cambridge University Press. 2005. ISBN 978-0-521-84328-7 （英語）. 
  38. ^ Gann, David; Salter, Ammon; Dodgson, Mark; Philips, Nelson. Inside the world of the project baron. MIT Sloan Management Review. 2012, 53 (3): 63–71. ISSN 1532-9194 （英語）. 
  39. ^ Meng, Xianhai. The effect of relationship management on project performance in construction. International Journal of Project Management. 2012, 30 (2): 188–198. doi:10.1016/j.ijproman.2011.04.002 （英語）. 
  40. ^ Oliveira, Nuno; Lumineau, Fabrice. How Coordination Trajectories Influence the Performance of Interorganizational Project Networks. Organization Science. 2017, 28 (6): 1029–1060. ISSN 1047-7039. doi:10.1287/orsc.2017.1151. 
  41. ^ Cohen Kashi S., Rozenes S. & Ben-Gal, I. (2016). Project Management Monitoring Based on Expected Duration Entropy (PDF). In Entropy 2020, 22, 905. 
  42. ^ Jörg Becker, Martin Kugeler, Michael Rosemann (2003). Process management: a guide for the design of business processes. ISBN 978-3-540-43499-3. p.27.
  43. ^ Bernhard Schlagheck (2000). Objektorientierte Referenzmodelle für das Prozess- und Projektcontrolling. Grundlagen – Konstruktionen – Anwendungsmöglichkeiten. ISBN 978-3-8244-7162-1. p.131.
  44. ^ Josef E. Riedl (1990). Projekt – Controlling in Forschung und Entwicklung. ISBN 978-3-540-51963-8. p.99.
  45. ^ Steinle, Bruch, Lawa (1995). Projektmanagement. FAZ Verlagsbereich Wirtschaftsbücher. p.136–143
  46. ^ Cynthia Snyder, Frank Parth (2006). Introduction to IT Project Management. p.393-397
  47. ^ Abdou, Saed M; Yong, Kuan; Othman, Mohammed. Project Complexity Influence on Project management performance – The Malaysian perspective. MATEC Web of Conferences. 2016, 66: 00065. ISSN 2261-236X. doi:10.1051/matecconf/20166600065   （英語）. 
  48. ^ Ludovic‐Alexandre Vidal, Franck Marle, Vidal. Understanding project complexity: implications on project management (PDF). Kybernetes. 2008, 37 (8): 1094–1110. doi:10.1108/03684920810884928. 
  49. ^ G., Morris, Peter W. The management of projects. London: T. Telford. 1994: 317. ISBN 978-0727725936. OCLC 30437274. 
  50. ^ Gower handbook of people in project management. Lock, Dennis., Scott, Lindsay, 1974-. Farnham, Surrey: Gower Publishing. 2013: 398. ISBN 978-1409437857. OCLC 855019788. 
  51. ^ PMOs. www.theprojectmanager.co.za. [2018-03-01] （英語）. 
  52. ^ Commission, Australian Public Service. APS framework for optimal management structures. [2018-03-01] （英語）. 
  53. ^ Bannerman, P. L. (2008). Defining project success: a multilevel framework. Paper presented at PMI® Research Conference: Defining the Future of Project Management, Warsaw, Poland. Newtown Square, PA: Project Management Institute. Available at https://www.pmi.org/learning/library/defining-project-success-multilevel-framework-7096
  54. ^ Emanuel Camilleri, Project Success: Critical Factors and Behaviours, Gower Publishing, Ltd., 2011
  55. ^ DoDD 5000.01 (PDF). United States Department of Defense. [20 November 2007]. 
  56. ^ 56.0 56.1 NASA NPR 9501.2D. May 23, 2001.
  57. ^ ISO/IEC/IEEE 16326-2009 – Systems and Software Engineering--Life Cycle Processes--Project Management. December 2009. DOI: 10.1109/IEEESTD.2009.5372630. ISBN 978-0-7381-6116-7
  58. ^ Individual Competence Baseline for Project, Programme & Portfolio Management (PDF). International Project Management Association (IPMA). 2015. ISBN 978-94-92338-01-3. 
  59. ^ Albert Hamilton (2004). Handbook of Project Management Procedures. TTL Publishing, Ltd. ISBN 0-7277-3258-7
  60. ^ PMBOK 4h Ed.. 2008: 443. ISBN 978-1933890517. 
  61. ^ Tom Kendrick. The Project Management Tool Kit: 100 Tips and Techniques for Getting the Job Done Right, Third Edition. AMACOM Books, 2013 ISBN 9780814433454
  62. ^ Curlee, Wanda. The Virtual Project Management Office: Best Practices, Proven Methods. 2011. 
  63. ^ Khazanchi, Deepak. Patterns of Effective Project Management in Virtual Projects: An Exploratory Study. Project Management Institute. 2005 [2013-10-22]. ISBN 9781930699830. （原始內容存檔於2013-10-23）. 
  64. ^ Velagapudi, Mridula. Why You Cannot Avoid Virtual Project Management 2012 Onwards. April 13, 2012. 
取自「https://zh.wikipedia.org/w/index.php?title=User:VKeksburg/沙盒/项目管理&oldid=65815595」