- •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
ISO/TC 236 N 113
ISO/TC 236
ISO/TC 236 - Project Committee: Project Management
Email of secretary: karl.best@pmi.org
Secretariat: ANSI (USA)
21500 FDIS
Document type: |
Other draft |
Date of document: |
2012-03-13 |
Expected action: |
INFO |
Background: |
This is the version of 21500 submitted to ISO for FDIS ballot. |
Committee URL: |
http://isotc.iso.org/livelink/livelink/open/tc236 |
(c) ISO 2012 – All rights reserved
ISO PC 236/ N 113
Date: 2012-03-13
ISO/FDIS 21500
ISO PC 236
Secretariat: ANSI
Guidance on project management
(version submitted to ISO for FDIS)
Copyright notice
This ISO document is a working draft or committee draft and is copyright-protected by ISO. While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from ISO.
Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO's member body in the country of the requester:
[Indicate the full address, telephone number, fax number, telex number, and electronic mail address, as appropriate, of the Copyright Manager of the ISO member body responsible for the secretariat of the TC or SC within the framework of which the working document has been prepared.]
Reproduction for sales purposes may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
Contents |
Page |
|
Foreword................................................................................................................................... |
4 |
|
Introduction .............................................................................................................................. |
5 |
|
1 |
Scope ........................................................................................................................... |
6 |
2 |
Terms and definitions................................................................................................. |
7 |
3 |
Project management concepts.................................................................................. |
9 |
3.1 |
General......................................................................................................................... |
9 |
3.2 |
Project ........................................................................................................................ |
10 |
3.3 |
Project management................................................................................................. |
10 |
3.4 |
Organizational strategy and projects ..................................................................... |
10 |
3.5 |
Project environment ................................................................................................. |
11 |
3.6 |
Project governance................................................................................................... |
12 |
3.7 |
Projects and operations ........................................................................................... |
13 |
3.8 |
Stakeholders and project organization .................................................................. |
13 |
3.9 |
Competencies of project personnel........................................................................ |
14 |
3.10 |
Project life cycle........................................................................................................ |
15 |
3.11 |
Project constraints ................................................................................................... |
15 |
3.12 |
Relationship between project management concepts and processes ............... |
16 |
4 |
Project management processes.............................................................................. |
17 |
4.1 |
Project management process application.............................................................. |
17 |
4.2 |
Process groups and subject groups ...................................................................... |
17 |
4.3 |
Processes .................................................................................................................. |
22 |
Annex A (informative) Process group processes mapped to subject groups................. |
44 |
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 21500 was prepared by Project Committee ISO/PC 236, Project Management.
Introduction
This International Standard provides guidance on concepts and processes of project management that are important for and have impact on the performance of projects.
The target readership for this standard is:
senior managers and project sponsors so that they may better understand the principles and practice of project management to facilitate providing appropriate support and guidance to their project managers, project management teams, and the project teams;
project managers, project management teams, and project team members so that they may have a common base of comparison of their project standards and practices with those of others; and
developers of national or organizational standards for use in developing project management standards, which are consistent at a core level with those of others.
This International Standard is not intended for certification or regulatory purposes.
1 Scope
This International Standard provides guidance for project management and may be used by any type of organization, including public, private or community organizations; and for any type of project, irrespective of complexity, size, or duration.
This standard provides high-level description of concepts and processes that are considered to form good practice in project management. Projects are placed in the context of programmes and project portfolios, however, this standard does not provide detailed guidance on the management of programmes and project portfolios. Topics pertaining to general management are addressed only within the context of project management.
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1 activity
identified component of work within a schedule that is required to be undertaken to complete a project
2.2
application area
category of projects that generally have a common focus related to a product, customer, or sector
2.3 baseline
reference basis for comparison against which project performance is monitored and controlled
2.4
change request
documentation that defines a proposed alteration to the project
2.5
configuration management
application of procedures to control, correlate, and maintain documentation, specifications and physical attributes
2.6 control
comparison of actual performance with planned performance, analyzing variances, and taking appropriate corrective and preventive action as needed
2.7
corrective action
direction and activity for modifying the performance of work to bring performance in line with the plan
2.8
critical path
sequence of activities that determine the earliest possible completion date for the project or phase
2.9 lag
attribute applied to a logical relationship to delay the start or end of an activity
2.10 lead
attribute applied to a logical relationship to advance the start or end of an activity
2.11
preventive action
direction and activity for modifying the work to avoid or reduce potential deviations in performance from the plan
2.12
project life cycle
defined set of phases from the start to the end of the project
2.13
risk register
record of identified risks including results of analysis and planned responses
2.14 stakeholder
person, group or organization that has interests in or can affect, be affected by, or perceive themselves to be affected by any aspect of the project
2.15 tender
document in the form of an offer or statement of bid to supply a product , service, or result usually in response to an invitation or request
2.16
work breakdown structure dictionary
document that describes each component in the work breakdown structure