- •Introduction
- •1 Scope
- •2 Terms and definitions
- •3 Project management concepts
- •3.1 General
- •3.2 Project
- •3.3 Project management
- •3.4 Organizational strategy and projects
- •3.4.1 Organizational strategy
- •3.4.2 Opportunity evaluation and project initiation
- •3.4.3 Benefits realisation
- •3.5 Project environment
- •3.5.1 General
- •3.5.2 Factors outside the organizational boundary
- •3.5.3 Factors inside the organizational boundary
- •3.5.3.1 General
- •3.5.3.2 Project portfolio management
- •3.5.3.3 Programme management
- •3.6 Project governance
- •3.7 Projects and operations
- •3.8 Stakeholders and project organization
- •3.9 Competencies of project personnel
- •3.10 Project life cycle
- •3.11 Project constraints
- •3.12 Relationship between project management concepts and processes
- •4 Project management processes
- •4.1 Project management process application
- •4.2 Process groups and subject groups
- •4.2.1 General
- •4.2.2 Process groups
- •4.2.2.1 General
- •4.2.2.2 Initiating process group
- •4.2.2.3 Planning process group
- •4.2.2.4 Implementing process group
- •4.2.2.5 Controlling process group
- •4.2.2.6 Closing process group
- •4.2.2.7 Project management process group interrelationships and interactions
- •4.2.3 Subject groups
- •4.2.3.1 General
- •4.2.3.2 Integration
- •4.2.3.3 Stakeholder
- •4.2.3.4 Scope
- •4.2.3.5 Resource
- •4.2.3.6 Time
- •4.2.3.7 Cost
- •4.2.3.8 Risk
- •4.2.3.9 Quality
- •4.2.3.10 Procurement
- •4.2.3.11 Communication
- •4.3 Processes
- •4.3.1 General
- •4.3.2 Develop project charter
- •4.3.3 Develop project plans
- •4.3.4 Direct project work
- •4.3.5 Control project work
- •4.3.6 Control changes
- •4.3.7 Close project phase or project
- •4.3.8 Collect lessons learned
- •4.3.9 Identify stakeholders
- •4.3.10 Manage stakeholders
- •4.3.11 Define scope
- •4.3.12 Create work breakdown structure
- •4.3.13 Define activities
- •4.3.14 Control scope
- •4.3.15 Establish project team
- •4.3.16 Estimate resources
- •4.3.17 Define project organization
- •4.3.18 Develop project team
- •4.3.19 Control resources
- •4.3.20 Manage project team
- •4.3.21 Sequence activities
- •4.3.22 Estimate activity durations
- •4.3.23 Develop schedule
- •4.3.24 Control schedule
- •4.3.25 Estimate costs
- •4.3.26 Develop budget
- •4.3.27 Control costs
- •4.3.28 Identify risks
- •4.3.29 Assess risks
- •4.3.30 Treat risks
- •4.3.31 Control risks
- •4.3.32 Plan quality
- •4.3.33 Perform quality assurance
- •4.3.34 Perform quality control
- •4.3.35 Plan procurements
- •4.3.36 Select suppliers
- •4.3.37 Administer procurements
- •4.3.38 Plan communications
- •4.3.39 Distribute information
- •4.3.40 Manage communications
needs of the stakeholders and any mandated information needs, for example, government or regulatory, and determining a suitable means of meeting those needs.
Factors such as geographically dispersed personnel, multiple cultures, and organizational factors may significantly affect communication requirements. For further information see 3.5.1.
This process should begin early in the planning of the project following a stakeholder identification and analysis, and should be regularly reviewed and revised as needed to ensure continued effectiveness throughout the project. The communications plan defines the information requirements and should be easily accessible by the appropriate stakeholders throughout the project.
The primary inputs and outputs are listed in Table 38.
Table 38 — Plan communications: primary inputs and outputs
Primary Inputs |
Primary Outputs |
|
|
|
|
Project plans |
Communications plan |
|
Stakeholder register |
|
|
|
Role descriptions |
|
|
Approved changes |
|
|
|
|
4.3.39 Distribute information
The purpose of Distribute information is to make required information available to project stakeholders as defined by the communications plan and responding to unexpected, ad-hoc requests for information.
Organizational policies, procedures and other information may be amended, provided, or affected as a result of this process.
The primary inputs and outputs are listed in Table 39.
Table 39 — Distribute information: primary inputs and outputs
Primary Inputs |
Primary Outputs |
|
|
|
|
Communications plan |
Distributed information |
|
|
Progress reports |
|
|
Unexpected requests |
|
|
|
|
4.3.40 Manage communications
The purpose of Manage communications is to ensure that the communication needs of the project stakeholders are satisfied and to resolve communication issues if and when they arise.
Success or failure of a project may depend on how well the various project team members and stakeholders communicate with each other. This process should focus on increasing the understanding and cooperation among the various stakeholders through good communications; providing timely, accurate and unbiased information; and resolving communication issues to
minimise the risk that the project is negatively affected by unknown or unresolved stakeholder issues or misunderstandings.
The primary inputs and outputs are listed in Table 40.
Table 40 — Manage communications: primary inputs and outputs
Primary Inputs |
Primary Outputs |
||
|
|
|
|
|
Communications plan |
|
Accurate and timely information |
|
Distributed information |
|
Corrective actions |
|
|
|
|
Annex A
(informative)
Process group processes mapped to subject groups
This annex provides a depiction of the interactions of the individual processes in each process group identified in 4.2.2 mapped to the subject groups identified in 4.2.3. Not all process interactions are depicted and the interactions depicted represent only one possible logic view of the processes.
Not all process interactions are depicted in the figures. The arrows represent one logic sequence of processes and it is up to some combination of the organization, project manager, project management team, and project team to decide what processes are required and in what sequence. Any process may be repeated.
(c) ISO 2012 – All rights reserved
Process |
|
|
|
Group |
|
|
Initiating |
Subject |
|
|
|
Groups |
|
|
|
1 |
|
4.3.2 |
|
|
|
Develop |
1 |
Integration |
Start |
project |
|
|
|
charter |
|
2 |
|
|
4.3.9 |
|
|
|
|
Stakeholder |
|
|
Identify |
|
|
|
stakeholders |
3 |
|
|
|
Scope |
|
|
|
4 |
|
|
4.3.15 |
|
|
|
|
Ressources |
|
|
Establish |
|
|
|
project team |
5 |
|
|
|
Time |
|
|
|
6 |
|
|
|
Cost |
|
|
|
7 |
|
|
|
Risk |
|
|
|
8 |
|
|
|
Quality |
|
|
|
9 |
|
|
|
Procurement |
|
|
|
10 |
|
|
|
Communication |
|
|
|
Not all process interactions are depicted in the figure. The arrows represent one logic sequence of processes and it is up to some combination of the organization, project manager,project management team, and project team to decide what processes are required and in what sequence. Any process may be repeated.
Figure A-1 Initiating process group processes
Process |
|
|
|
|
|
|
|
|
Group |
|
|
|
Planning |
|
|
|
|
Subject |
|
|
|
|
|
|
||
Groups |
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
4.3.3 |
|
|
Integration |
1 |
|
|
|
|
Develop |
2 |
|
|
|
|
|
|
project plans |
|||
|
|
|
|
|
|
|||
2 |
|
|
|
|
|
|
|
|
Stakeholder |
|
|
|
|
|
|
|
|
3 |
4.3.11 |
4.3.12 |
4.3.13 |
|
|
|
|
|
|
|
|
|
|
|
|||
Scope |
Define |
Create WBS |
Define |
|
|
|
|
|
|
scope |
activities |
|
|
|
|
|
|
|
|
|
|
|
|
|
||
4 |
|
|
|
|
4.3.16 |
4.3.17 |
|
|
|
|
|
|
|
|
|
||
Ressources |
|
|
|
|
Estimate |
Define project |
|
|
|
|
|
|
|
resources |
organisation |
|
|
5 |
|
|
4.3.21 |
4.3.22 |
4.3.23 |
|
|
|
|
|
|
|
|
|
|
||
Time |
|
|
Sequence |
Estimate |
Develop |
|
|
|
|
|
activity |
|
|
|
|||
|
|
|
acitivities |
schedule |
|
|
|
|
|
|
|
durations |
|
|
|
||
|
|
|
|
|
|
|
|
|
6 |
|
|
|
4.3.25 |
4.3.26 |
|
|
|
|
|
|
|
|
|
|
||
Cost |
|
|
|
Estimate |
Develop |
|
|
|
|
|
|
|
costs |
budget |
|
|
|
7 |
|
|
|
|
|
4.3.28 |
4.3.29 |
|
|
|
|
|
|
|
|||
Risk |
|
|
|
|
|
Identify |
|
Assess |
|
|
|
|
|
|
risks |
|
risks |
8 |
|
4.3.32 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quality |
|
Plan quality |
|
|
|
|
|
|
9 |
|
|
|
|
|
4.3.35 |
|
|
|
|
|
|
|
|
|
|
|
Procurement |
|
|
|
|
|
Plan |
|
|
|
|
|
|
|
|
procurements |
|
|
10 |
|
|
|
|
|
4.3.38 |
|
|
|
|
|
|
|
|
|
|
|
Communication |
|
|
|
|
|
Plan |
|
|
|
|
|
|
|
|
communications |
|
|
Not all process interactions are depicted in the figure. The arrows represent one logic sequence of processes and it is up to some combination of the organization, project manager,project management team, and project team to decide what processes are required and in what sequence. Any process may be repeated.
Figure A-2 Planning process group processes
Process |
|
|
|
Group |
|
|
Implementing |
Subject |
|
|
|
Groups |
|
|
|
1 |
|
4.3.4 |
|
Integration |
2 |
Direct project |
3 |
|
work |
|
|
|
|
|
|
2 |
|
|
4.3.10 |
|
|
|
|
Stakeholder |
|
|
Manage |
|
|
|
stakeholders |
3 |
|
|
|
Scope |
|
|
|
4 |
|
|
4.3.18 |
|
|
|
|
Ressources |
|
|
Develop |
|
|
|
project team |
5 |
|
|
|
Time |
|
|
|
6 |
|
|
|
Cost |
|
|
|
7 |
|
|
4.3.30 |
|
|
|
|
Risk |
|
|
Treat |
|
|
|
risks |
8 |
|
|
4.3.33 |
|
|
|
|
Quality |
|
|
Perform |
|
|
quality |
|
|
|
|
assurance |
9 |
|
|
4.3.36 |
|
|
|
|
Procurement |
|
|
Select |
|
|
|
suppliers |
10 |
|
|
4.3.39 |
|
|
|
|
Communication |
|
|
Distribute |
|
|
|
information |
Not all process interactions are depicted in the figure. The arrows represent one logic sequence of processes and it is up to some combination of the organization, project manager,project management team, and project team to decide what processes are required and in what sequence. Any process may be repeated.
Figure A-3 Implementing process group processes
Process |
|
|
|
Group |
|
Controlling |
|
Subject |
|
||
Groups |
|
|
|
1 |
4.3.5 |
4.3.6 |
|
|
|
||
Integration |
Control |
Control |
|
|
project work |
changes |
|
2 |
|
|
|
Stakeholder |
|
|
|
3 |
|
4.3.14 |
|
|
|
|
|
Scope |
|
Control |
|
|
|
scope |
|
4 |
|
4.3.19 |
4.3.20 |
|
|
||
Ressources |
|
Control |
Manage |
|
|
resources |
project team |
5 |
|
4.3.24 |
|
|
|
|
|
Time |
|
Control |
|
|
|
schedule |
|
6 |
|
4.3.27 |
|
Cost |
|
Control |
|
|
costs |
|
|
|
|
|
|
7 |
|
4.3.31 |
|
|
|
|
|
Risk |
|
Control |
|
|
|
risks |
|
8 |
|
4.3.34 |
|
|
|
|
|
Quality |
|
Perform |
|
|
quality control |
|
|
|
|
|
|
9 |
|
4.3.37 |
|
Procurement |
|
Administer |
|
|
procurements |
|
|
|
|
|
|
10 |
|
4.3.40 |
|
|
|
|
|
Communication |
|
Manage |
|
|
|
communications |
|
Not all process interactions are depicted in the figure. The arrows represent one logic sequence of processes and it is up to some combination of the organization, project manager,project management team, and project team to decide what processes are required and in what sequence. Any process may be repeated.
Figure A-4 Controlling process group processes
Process |
|
|
|
|
Group |
|
|
|
Closing |
Subject |
|
|
|
|
Groups |
|
|
|
|
1 |
3 |
4.3.7 |
4.38 Collect |
|
Integration |
Close phase |
lessons |
End |
|
|
or project |
|||
|
|
learned |
|
|
|
|
|
|
|
2 |
|
|
|
|
Stakeholder |
|
|
|
|
3 |
|
|
|
|
Scope |
|
|
|
|
4 |
|
|
|
|
Ressources |
|
|
|
|
5 |
|
|
|
|
Time |
|
|
|
|
6 |
|
|
|
|
Cost |
|
|
|
|
7 |
|
|
|
|
Risk |
|
|
|
|
8 |
|
|
|
|
Quality |
|
|
|
|
9 |
|
|
|
|
Procurement |
|
|
|
|
10 |
|
|
|
|
Communication |
|
|
|
|
Not all process interactions are depicted in the figure. The arrows represent one logic sequence of processes and it is up to some combination of the organization, project manager,project management team, and project team to decide what processes are required and in what sequence. Any process may be repeated.
Figure A-5 Closing process group processes