IEEE P16326 DRAFT
Systems and software engineering - Life cycle processes - Project management
|Publication Date:||1 December 2018|
This document is intended to aid project managers in managing to successful conclusion those projects concerned with software-intensive systems and software products.
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:2015  and ISO/IEC/IEEE 12207:2017  and adds detailed guidance for managing projects that use these processes for software products and software-intensive systems.
Field of application
This document is written for those who use or plan to use ISO/IEC/IEEE 15288:2015  and ISO/IEC/IEEE 12207:2017  on projects dealing with software-intensive systems and software products, 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:2015  system life cycle processes and ISO/IEC/IEEE 12207:2017  software life cycle processes.
- Those responsible for executing any ISO/IEC/IEEE 15288:2015  system life cycle process or ISO/IEC/IEEE 12207:2017  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 should be taken as applying to the applicable role within the organization.
This document is intended to provide guidance for two-party situations and may be equally applied where the two parties are from the same organization. This document may 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 may involve several vendors, organizations or contracting parties.
The normative content specifications for PMPs and the guidance for application of the technical management processes are limited to projects dealing with software-intensive systems and software products.