Exposure draft

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Appendix E - Application Area Extensions

Exposure Draft

E.1 Need for Application Area Extensions

Application area extensions are necessary when there are generally accepted knowledge and practices for a category of projects (an application area) that are not generally accepted across the full range of project types. Application area extensions reflect:

Unique or unusual aspects of the project environment that the project management team must be aware of in order to manage the project efficiently and effectively.

Common knowledge and practices which, if followed, will improve the efficiency and effectiveness of the project (e.g., standard work breakdown structures).

Application-area-specific knowledge and practices can arise as a result of many factors, including, but not limited to, differences in cultural norms, technical terminology, societal impact, or project life cycles. For example:

In construction, where virtually all work is accomplished under contract, there are common knowledge and practices related to procurement that do not apply to all categories of projects.

In biosciences, there are common knowledge and practices driven by the regulatory environment that do not apply to all categories of projects.

In government contracting, there are common knowledge and practices driven by government acquisition regulations that do not apply to all categories of projects.

In consulting, there are common knowledge and practices created by the project manager's sales and marketing responsibilities that do not apply to all categories of projects.

Application area extensions are additions to the core material of Chapters 1 through 12, not substitutes for it. Extensions will be organized in a fashion similar to the PMBOK Guide; i.e., by identifying and describing the project management processes peculiar to that application area. In different application areas, there may be a need to identify additional processes, to subdivide common processes, to define different sequences or process interactions, or to add elements to the common process definitions. Extensions will match the PMBOK Guide in style and content and they will use the paragraph and subparagraph numbers of the PMBOK Guide material that has been extended. Sections and paragraphs of the PMBOK Guide that are not extended will not be repeated in extensions.

Extensions Development and Maintenance

Figure E-1. Extensions Development and Maintenance

Extensions are not “how to” documents or “practice standards.” Such documents may be published as Standards Documents by PMI but they are not what are intended as extensions of the PMBOK Guide. Similarly, extensions are not a lower level of detail than is addressed in the PMBOK Guide. That may be addressed in handbooks or guidebooks and may be published by PMI or others, but, again, it is not what is intended for extensions.

E.2 Criteria for Development of Application Area Extensions

Extensions will be developed for those application areas that meet the following criteria:

There is a substantial body of knowledge that is both project-oriented and unique or nearly unique to that application area.

There is an identifiable organization (e.g., a PMI Specific Interest Group) willing to commit the necessary resources to support the PMI Standards Committee with developing and maintaining the material.

The extension is able to pass the same level of rigorous Standards Committee review and exposure draft process as the PMBOK Guide.

E.3 Publishing and Format of Application Area Extensions

Application area extensions are original works, as defined by Appendix A to this PMBOK Guide. They are published by PMI and bound as individual documents.

Extensions match the PMBOK Guide in style and content. They use the paragraph and subparagraph numbers of the PMBOK Guide material that has been extended.

Sections and paragraphs of the PMBOK Guide that are not extended are not repeated in extensions.

They contain a rationale/justification for the extension and its material.

They are delimited in terms of what they are not intended to do.

E.4 Process for Development and Maintenance

Extensions, when approved, become PMI Standards Documents. Accordingly, they must comply with the provisions of Appendix A to this PMBOK Guide. Additionally extensions will be developed and maintained in accordance with the process described below and on the deployment flow chart (Figure E-1).

An extension must be sponsored by a formally chartered sub-organization of PMI (e.g., a Specific Interest Group).

The sponsoring group will notify and solicit advice and support from the SIG Council throughout the development and maintenance process. The SIG Council will concur with the appropriateness of the sponsoring organization for the extension proposed and will review the extension during its development to identify any conflicts or overlaps with other similar projects that may be under way. Comments to the PMI Standards Committee will be solicited from all SIGs on the extension as finally submitted for approval.

The sponsoring group will prepare a proposal for approval to develop the extension, including a justification for the effort with a matrix of application-area-specific processes and the affected sections of the PMBOK Guide; the commitment of sufficient qualified drafters and reviewers, identification of funding requirements, including reproduction, postage, telephone costs, desktop publishing, etc.; commitment to the PMI procedures for extension development and maintenance; and a plan and schedule for same.

The proposal will include sources of funding and any funding proposed to be provided by PMI.

The proposal will include a requirement for periodic review of the extension with reports to the PMI Standards Committee and a “Sunset Clause” that specifies when, and under what conditions, the extension will be removed from status as a PMI Standards Document.

The proposal will be submitted to the PMI Director of Standards in accordance with paragraph A.2, Appendix A, to this PMBOK Guide. The Director of Standards will determine if the proposal can be expected to result in a document that will meet the requirements for a PMI Standards Document and if adequate resources and sources of support have been identified. To help with this determination, the Director of Standards may seek review and comment by a panel of knowledgeable persons not involved with the extension.

The PMI Director of Standards, with the support of the PMI Standards Committee, will monitor and support the development of approved proposals in accordance with Appendix A to this PMBOK Guide.

The sponsoring organization will develop the extension according to the approved proposal, including coordinating with the SIG Council for support, review and comment.

When the extension has been completed to the satisfaction of the sponsoring organization, it will be submitted to the PMI Director of Standards, who will manage the final approval and publication processes in accordance with Appendix A to this PMBOK Guide. This final submittal will include an updated and renewed listing of and commitment by the sponsoring organization to the PMI extension maintenance processes and efforts.

The sponsoring organization will implement the extension maintenance process in accordance with the approved plan. ■

PM Network • November 1997

Advertisement

Advertisement

Related Content

  • Project Management Journal

    Getting Past the Editor's Desk member content locked

    By Klein, Gary | Müller, Ralf To reach acceptance, every research paper submitted to Project Management Journal® (PMJ) must pass several hurdles. This editorial aims to declare the editorial process and reveal major reasons for…

  • Project Management Journal

    Coordinating Lifesaving Product Development Projects with no Preestablished Organizational Governance Structure member content locked

    By Leme Barbosa, Ana Paula Paes | Figueiredo Facin, Ana Lucia | Sergio Salerno, Mario | Simões Freitas, Jonathan | Carelli Reis, Marina | Paz Lasmar, Tiago We employed a longitudinal, grounded theory approach to investigate the management of an innovative product developed in the context of a life-or-death global emergency.

  • Project Management Journal

    Narratives of Project Risk Management member content locked

    By Green, Stuart D. | Dikmen, Irem The dominant narrative of project risk management pays homage to scientific rationality while conceptualizing risk as objective fact.

  • Project Management Journal

    Investigating the Dynamics of Engineering Design Rework for a Complex Aircraft Development Project member content locked

    By Souza de Melo, Érika | Vieira, Darli | Bredillet, Christophe The purpose of this research is to evaluate the dynamics of EDR that negatively impacts the performance of complex PDPs and to suggest actions to overcome those problems.

  • Project Management Journal

    Navigating Tensions to Create Value member content locked

    By Farid, Parinaz | Waldorff, Susanne Boche This article employs institutional logics to explore the change program–organizational context interface, and investigates how program management actors navigate the interface to create value.

Advertisement