BS ISO/IEC 16326:2009 Systems and software engineering. Life cycle processes. Project management
BS ISO/IEC 16326 is intended to aid project managers in managing to successful conclusion those projects concerned with software-intensive systems and software products.
BS ISO/IEC 16326 specifies the required content of the project management plan (PMP). This International Standard also quotes the extracted purpose and outcome statements from the project processes of ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and adds detailed guidance for managing projects that use these processes for software products and software intensive systems.
BS ISO/IEC 16326 is written for those who use or plan to use ISO/IEC 15288:2008 (IEEE Std 15288- 2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) on projects dealing with software-intensive systems and software products, regardless of project scope, product, methodology, size or complexity. The field of application of this International Standard spans the whole software or system life cycle, and addresses everybody who plays a role in project management – project managers and others, specifically:
- Those responsible for establishing and continuously improving ISO/IEC 12207:2008 (IEEE Std 12207- 2008) software life cycle processes and ISO/IEC 15288:2008 (IEEE Std 15288-2008) system life cycle processes
- Those responsible for executing any ISO/IEC 12207:2008 (IEEE Std 12207-2008) software life cycle process or ISO/IEC 15288:2008 (IEEE Std 15288-2008) system 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 BS ISO/IEC 16326, the guidance, advice or normative requirement applies to the applicable role within the organization.
BS ISO/IEC 16326 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.
The normative content specifications for project management plans and the guidance for management of the project processes are limited to projects dealing with software-intensive systems and software products.
BS ISO/IEC 16326 provides normative content specifications for project management plans covering software projects, and software-intensive system projects. It also provides detailed discussion and advice on applying a set of project processes that are common to both the software and system life cycle as covered by ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering. Software life cycle processes, and ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering. System life cycle processes, respectively. The discussion and advice are intended to aid in the preparation of the normative content of project management plans.
Contents of BS ISO/IEC 16326 include:- Foreword
- Introduction
- Purpose
- Field of application
- Limitations
- Conformance to normative documentation content
- Conformance to processes
- Full conformance
- Symbols and abbreviations
- Application of this International Standard
- Elements of the project management plan
- Project overview (Clause 1 of the PMP)
- Project summary (Subclause 1.1 of the PMP)
- Evolution of the plan (Subclause 1.2 of the PMP)
- References (Clause 2 of the PMP)
- Definitions (Clause 3 of the PMP)
- Project context (Clause 4 of the PMP)
- Process model (Clause 4.1 of the PMP)
- Process improvement plan (Clause 4.2 of the PMP)
- Infrastructure plan (Clause 4.3 of the PMP)
- Methods, tools and techniques (Clause 4.4 of the PMP)
- Product acceptance plan (Clause 4.5 of the PMP)
- Project organization (Clause 4.6 of the PMP).
- Project planning (Clause 5 of the PMP)
- Project initiation (Subclause 5.1 of the PMP)
- Project work plans (Subclause 5.2 of the PMP)
- Requirements management plan (Subclause 6.1 of the PMP)
- Scope change control plan (Subclause 6.2 of the PMP)
- Schedule control plan (Subclause 6.3 of the PMP)
- Budget control plan (Subclause 6.4 of the PMP)
- Quality assurance plan (Subclause 6.5 of the PMP)
- Subcontractor management plans (Subclause 6.6 of the PMP)
- Project closeout plan (Subclause 6.7 of the PMP)
- Product delivery (Clause 7 of the PMP) 1
- Supporting process plans (Clause 8 of the PMP)
- Project supervision and work environment (Subclause 8.1 of the PMP)
- Decision management (Subclause 8.2 of the PMP)
- Risk management (Subclause 8.3 of the PMP)
- Configuration management (Subclause 8.4 of the PMP)
- Information management (Subclause 8.5 of the PMP)
- Quality assurance (Subclause 8.6 of the PMP)
- Measurement (Subclause 8.7 of the PMP)
- Reviews and audits (Subclause 8.8 of the PMP)
- Verification and validation (Subclause 8.9 of the PMP)
- Additional plans (Clause 9 of the PMP)
- End matter
- Project processes
- Project planning process
- Project assessment and control process
- Decision management process
- Risk management process
- Configuration management process
- Information management process
- Measurement process
- Format of a project management plan
