Systems and software engineering — Life cycle processes — Project management

1.1 Purpose This document is intended to aid project managers in managing to successful conclusion those projects concerned with systems, including software systems. This document specifies the required content of the project management plan (PMP). This document also quotes the extracted purpose and outcome statements from the technical management processes of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, and adds detailed guidance for managing projects that use these processes for systems, including software systems. 1.2 Field of application This document is written for those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 on projects dealing with systems, including software systems, regardless of project scope, products, methodology, size or complexity. The field of application of this document spans the whole system or software life cycle and addresses all project management roles, specifically: — those responsible for establishing and continuously improving their organization's policies for implementing ISO/IEC/IEEE 15288 system life cycle processes and ISO/IEC/IEEE 12207 software life cycle processes; — those responsible for executing any ISO/IEC/IEEE 15288 system life cycle process or ISO/IEC/IEEE 12207 software life cycle process at a project level. — organizations or individuals subcontracting a project management effort. In many organizations, the various responsibilities of project management are assigned to more than one person. Where the term "project manager" is used in this document, the guidance, advice or normative requirement is taken as applying to the applicable role within the organization. This document is intended to provide guidance for two-party situations and can be equally applied where the two parties are from the same organization. This document can also be used by a single party as self-imposed tasks. This document can also serve as guidance in multi-party situations, where high risks are inherent in the supply and integration of complex software-based systems, and procurement can involve several vendors, organizations or contracting parties. 1.3 Limitations The normative content specifications for PMPs and the guidance for application of the technical management processes have general application across the scope of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, but are developed with a focus on projects dealing with systems with a significant software element, and software systems.

Ingénierie du logiciel — Processus de cycle de vie — Gestion de projet

General Information

Status
Published
Publication Date
12-Dec-2019
Current Stage
6060 - International Standard published
Start Date
13-Dec-2019
Due Date
11-Apr-2021
Completion Date
13-Dec-2019
Ref Project

Relations

Buy Standard

Standard
ISO/IEC/IEEE 16326:2019 - Systems and software engineering -- Life cycle processes -- Project management
English language
29 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC/
STANDARD IEEE
16326
Second edition
2019-12
Systems and software engineering —
Life cycle processes — Project
management
Ingénierie du logiciel — Processus de cycle de vie — Gestion de projet
Reference number
ISO/IEC/IEEE 16326:2019(E)
©
ISO/IEC 2019
©
IEEE 2019

---------------------- Page: 1 ----------------------
ISO/IEC/IEEE 16326:2019(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2019
© IEEE 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO or IEEE at the
respective address below or ISO’s member body in the country of the requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
CH-1214 Vernier, Geneva NY 10016-5997, USA
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org Email: stds.ipr@ieee.org
Website: www.iso.org Website: www.ieee.org
Published in Switzerland
© ISO/IEC 2019 – All rights reserved
ii © IEEE 2019 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC/IEEE 16326:2019(E)

Contents Page
Foreword .v
Introduction .vii
1 Scope . 1
1.1 Purpose . 1
1.2 Field of application . 1
1.3 Limitations . 1
2 Normative References . 1
3 Terms, definitions and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 2
4 Conformance . 2
4.1 General . 2
4.2 Conformance to the normative documentation content . 2
4.3 Conformance to processes . 2
4.4 Full conformance. 3
5 Application of this document . 3
6 Technical management processes . 3
6.1 General . 3
6.2 Project planning process . 5
6.2.1 General. 5
6.2.2 Guidance. 5
6.2.3 Software-specific guidance . 8
6.3 Project assessment and control process . 9
6.3.1 General. 9
6.3.2 Guidance. 9
6.4 Decision management process.11
6.4.1 General.11
6.4.2 Guidance.11
6.5 Risk management process .13
6.5.1 General.13
6.5.2 Guidance.13
6.6 Configuration management process .14
6.6.1 General.14
6.6.2 Guidance.14
6.7 Information management process .15
6.7.1 General.15
6.7.2 Guidance.15
6.8 Measurement process .16
6.8.1 General.16
6.8.2 Guidance.16
6.9 Quality assurance process .17
6.9.1 General.17
6.9.2 Guidance.17
7 Elements of the project management plan .18
7.1 General .18
7.2 Front matter .18
7.3 Project overview .18
7.3.1 Project summary .18
7.4 References .19
7.5 Definitions .19
7.6 Project context.20
7.6.1 Process model .20
© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC/IEEE 16326:2019(E)

7.6.2 Process improvement .20
7.6.3 Infrastructure and enabling systems .20
7.6.4 Methods, tools and techniques .20
7.6.5 Product acceptance.20
7.6.6 Project organization .21
7.7 Project planning .21
7.7.1 General.21
7.7.2 Project initiation .21
7.7.3 Project work plans.22
7.8 Project assessment and control .23
7.8.1 General.23
7.8.2 Requirements management .23
7.8.3 Scope change control .24
7.8.4 Schedule control .24
7.8.5 Budget control .24
7.8.6 Quality assurance .24
7.8.7 Subcontractor management .24
7.8.8 Project closeout .24
7.9 Product delivery .25
7.10 Supporting processes .25
7.10.1 General.25
7.10.2 Project supervision and work environment .25
7.10.3 Decision management .25
7.10.4 Risk management .25
7.10.5 Configuration management .26
7.10.6 Information management .26
7.10.7 Quality assurance .27
7.10.8 Measurement .27
7.10.9 Reviews and audits .27
7.10.10 Verification and validation .27
7.11 Additional plans .28
7.12 End matter .28
Bibliography .29
IEEE notices and abstract .30
© ISO/IEC 2019 – All rights reserved
iv © IEEE 2019 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC/IEEE 16326:2019(E)

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that
are members of ISO or IEC participate in the development of International Standards through
technical committees established by the respective organization to deal with particular fields of
technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also
take part in the work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
rules given in the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its
standards through a consensus development process, approved by the American National Standards
Institute, which brings together volunteers representing varied viewpoints and interests to achieve the
final product. Volunteers are not necessarily members of the Institute and serve without compensation.
While the IEEE administers the process and establishes rules to promote fairness in the consensus
development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of
the information contained in its standards.
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www .iso .org/ patents) or the IEC
list of patent declarations received (see http:// patents .iec .ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso .org/
iso/ foreword .html.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Systems and software engineering, in cooperation with the Software & Systems
Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards
Development Organization cooperation agreement between ISO and IEEE.
This second edition cancels and replaces the first edition (ISO/IEC/IEEE 16326:2009), which has been
technically revised.
The main changes compared to the previous edition are as follows:
a) re-ordered the original Clauses 2 and 4, and added a new Clause 2 to comply with the new
ISO document fixed structure requirements;
b) moved the process guidelines up in front of the project management plan content requirements to
put more emphasis on the process rather than the “product;”
c) changed the citation tables in the new Clause 6 to a single column so that the corresponding content
is identical to both ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017;
d) added references in the applicable guidance portions of the new Clause 6 that point to
the more detailed process guidance information in ISO/IEC/IEEE 24748-4:2016 and
ISO/IEC/IEEE 24748-5:2017;
© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC/IEEE 16326:2019(E)

e) removed the PMP format requirements from the new Clause 7;
f) re-ordered the Bibliography to list the citations in numerical order.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
© ISO/IEC 2019 – All rights reserved
vi © IEEE 2019 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC/IEEE 16326:2019(E)

Introduction
This document provides normative content specifications for project management plans concerned
with systems, and software systems.
This document also provides detailed discussion and advice on applying a set of technical
management processes that are common to both the system and software life cycles as covered by
ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 respectively. The discussion and advice are intended to
aid in the preparation of the normative content of project management plans.
© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved vii

---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO/IEC/IEEE 16326:2019(E)
Systems and software engineering — Life cycle processes
— Project management
1 Scope
1.1 Purpose
This document is intended to aid project managers in managing to successful conclusion those projects
concerned with systems, including software systems.
This document specifies the required content of the project management plan (PMP). This document
also quotes the extracted purpose and outcome statements from the technical management processes
of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, and adds detailed guidance for managing projects
that use these processes for systems, including software systems.
1.2 Field of application
This document is written for those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207
on projects dealing with systems, including software systems, regardless of project scope, products,
methodology, size or complexity. The field of application of this document spans the whole system or
software life cycle and addresses all project management roles, specifically:
— those responsible for establishing and continuously improving their organization’s policies for
implementing ISO/IEC/IEEE 15288 system life cycle processes and ISO/IEC/IEEE 12207 software
life cycle processes;
— those responsible for executing any ISO/IEC/IEEE 15288 system life cycle process or
ISO/IEC/IEEE 12207 software life cycle process at a project level.
— organizations or individuals subcontracting a project management effort.
In many organizations, the various responsibilities of project management are assigned to more
than one person. Where the term "project manager" is used in this document, the guidance, advice or
normative requirement is taken as applying to the applicable role within the organization.
This document is intended to provide guidance for two-party situations and can be equally applied
where the two parties are from the same organization. This document can also be used by a single
party as self-imposed tasks.
This document can also serve as guidance in multi-party situations, where high risks are inherent in
the supply and integration of complex software-based systems, and procurement can involve several
vendors, organizations or contracting parties.
1.3 Limitations
The normative content specifications for PMPs and the guidance for application of the technical
management processes have general application across the scope of ISO/IEC/IEEE 15288 and
ISO/IEC/IEEE 12207, but are developed with a focus on projects dealing with systems with a significant
software element, and software systems.
2 Normative References
There are no normative references in this document.
© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved 1

---------------------- Page: 8 ----------------------
ISO/IEC/IEEE 16326:2019(E)

3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
No terms and definitions are listed in this document.
ISO, IEC and IEEE maintain terminological databases for use in standardization at the following
addresses:
— ISO Online browsing platform: available at http:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
— IEEE Standards Dictionary Online: available at http:// ieeexplore .ieee .org/ xpls/ dictionary
3.2 Abbreviated terms
CDRL contract data requirements list
ICWG interface control working group
PERT program evaluation review technique
PM project management (or project manager)
PMP project management plan
PPL product parts list
SDP software development plan
SEE software engineering environment
SEMP systems engineering management plan
SWEBoK software engineering body of knowledge
WBS work breakdown structure
4 Conformance
4.1 General
This document provides normative definition of the content of the PMP and provides guidance for the
execution of the technical management processes of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207.
Users of this document can claim conformance to the normative documentation content, to the process
provisions, or both.
4.2 Conformance to the normative documentation content
A claim of conformance to the documentation provisions of this document means that the user
demonstrates that the content of a PMP conforms to the content requirements specified in Clause 7.
4.3 Conformance to processes
A claim of conformance to the process provisions of this document is equivalent to claiming conformance
to the technical management processes from ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 cited in
Clause 6.
© ISO/IEC 2019 – All rights reserved
2 © IEEE 2019 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC/IEEE 16326:2019(E)

4.4 Full conformance
A claim of full conformance to this document is equivalent to claiming conformance to the PMP content
requirements cited in Clause 7 and the technical management processes of ISO/IEC/IEEE 15288 and
ISO/IEC/IEEE 12207 cited in Clause 6.
5 Application of this document
This document specifies the required content of the PMP such that the overall content of the plan, when
executed successfully, fulfils the purposes and desired outcomes which are specified by the technical
management processes of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207.
The technical management processes of ISO/IEC/IEEE 15288 and of ISO/IEC/IEEE 12207 contain the
generic activities and tasks, which can be employed by any party that has to manage a project dealing
with systems, including software systems. This document provides additional detailed guidance in
Clause 6 to assist managers of these projects as they prepare and execute the PMP for a specific project.
NOTE 1 In the general case, any specific project exists within an organization’s business program areas
and project portfolios. The organization can have additional processes that are not directly related to project
management, but that are essential to a project’s successful execution. The organizational project-enabling
processes in ISO/IEC/IEEE 15288 and the guidance in ISO 21500 provide useful information and guidance on
how a project’s technical management processes fit into the overall organization’s process structure.
NOTE 2 Reference [2] also provides important information about managing projects.
The responsible people listed as actors for which guidance applies are those most often tasked with
the listed preparation actions, but users of this document may agree to assign the actions to different
people or organizations depending on a given program’s organizational structure.
Project managers should also apply the guidance in this document in an iterative manner to c
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.