Project Management Body of Knowledge

Last updated
A Guide to the Project Management Body of Knowledge (the PMBOK Guide)
PMBOK.jpg
First edition
Author Project Management Institute
GenreBusiness
Published2021 (Project Management Institute)
Pages370 (seventh edition)
ISBN 978-1-62825-664-2

The Project Management Body of Knowledge (PMBOK) is a set of standard terminology and guidelines (a body of knowledge) for project management. The body of knowledge evolves over time and is presented in A Guide to the Project Management Body of Knowledge (PMBOK Guide), a book whose seventh edition was released in 2021. This document results from work overseen by the Project Management Institute (PMI), which offers the CAPM and PMP certifications.

Contents

Much of the PMBOK Guide is unique to project management such as critical path method and work breakdown structure (WBS). The PMBOK Guide also overlaps with general management regarding planning, organising, staffing, executing and controlling the operations of an organisation. Other management disciplines which overlap with the PMBOK Guide include financial forecasting, organisational behaviour, management science, budgeting and other planning methods.

History

Earlier versions of the PMBOK Guide were recognized as standards by the American National Standards Institute (ANSI) which assigns standards in the United States (ANSI/PMI 99-001-2008) and the Institute of Electrical and Electronics Engineers (IEEE 1490–2011). [1]

The evolution of the PMBOK Guide is reflected in editions of the Guide.

YearTitleRevision summary
1996PMBOK GuidePublished in 1996 by the Project Management Institute (PMI), this document evolved from a white paper published in 1983 called the "Ethics, Standards, and Accreditation Committee Final Report" with a different title and significantly reorganized. [2]
2000PMBOK Guide, 2000 EditionThe second edition (published as the 2000 Edition) added new material reflecting the growth of practices. [3] [4]
2004PMBOK Guide, Third EditionThe third edition (2004) was a significant edit from the earlier editions, changing criteria for inclusion from "generally accepted" practice to "generally recognized as good practice". [5]
2008PMBOK Guide, Fourth Edition [4]
2013PMBOK Guide, Fifth Edition [6]
2017PMBOK Guide, Sixth EditionThe sixth edition (September 2017) added several topics and included agile practices for the first time. [7]
2021PMBOK Guide, Seventh EditionThe seventh edition (2021) presents major structural changes, such as replacing the 10 knowledge areas with 12 principles and including agile practices more comprehensively. [8]

Purpose

The PMBOK Guide is intended to be a "subset of the project management body of knowledge" that is generally recognized as a good practice. 'Generally recognized' means the knowledge and practices described are applicable to most projects most of the time and there is a consensus about their value and usefulness. 'Good practice' means there is a general agreement that the application of the knowledge, skills, tools, and techniques can enhance the chance of success over many projects." [9] This means that sometimes the "latest" project management trends, often promoted by consultants, may not be part of the latest version of The PMBOK Guide.

However, the 6th Edition of the PMBOK Guide now includes an "Agile Practice Guide"

Contents

The PMBOK Guide is process-based, meaning it describes work as being accomplished by processes. This approach is consistent with other management standards such as ISO 9000 and the Software Engineering Institute's CMMI. Processes overlap and interact throughout a project or its various phases.

A Guide to the Project Management Body of Knowledge — Sixth Edition provides guidelines for managing individual projects and defines project management related concepts. It also describes the project management life cycle and its related processes, as well as the project life cycle. [9] and for the first time it includes an "Agile Practice Guide".

The PMBOK as described in the Guide recognizes 49 processes that fall into five basic process groups and ten knowledge areas that are typical of most projects, most of the time.

Process groups

The five process groups are:

  1. Initiating: processes performed to define a new project or a new phase of an existing project by obtaining authorization to start the project or phase.
  2. Planning: Those processes required to establish the scope of the project, refine the objectives, and define the course of action required to attain the objectives that the project was undertaken to achieve.
  3. Executing: Those processes performed to complete the work defined in the project management plan to satisfy the project specifications
  4. Monitoring and Controlling: Those processes required to track, review, and regulate the progress and performance of the project; identify any areas in which changes to the plan are required; and initiate the corresponding changes.
  5. Closing: Those processes performed to finalize all activities across all Process Groups to formally close the project or phase.

Knowledge areas

The ten knowledge areas, each of which contains some or all of the project management processes, are:

  1. Project Integration Management  : the processes and activities needed to identify, define, combine, unify, and coordinate the various processes and project management activities within the project management process groups.
  2. Project Scope management : the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.
  3. Project Schedule Management : the processes required to manage the timely completion of the project. Until the 6th edition of the PMBOK Guide this was called "Project Time Management"
  4. Project Cost Management  : the processes involved in planning, estimating, budgeting, financing, funding, managing, and controlling costs so that the project can be completed within the approved budget.
  5. Project Quality Management  : the processes and activities of the performing organization that determine quality policies, objectives, and responsibilities so that the project will satisfy the needs for which it was undertaken.
  6. Project Resource Management  : the processes that organize, manage, and lead the project team. Until the 6th edition of the PMBOK Guide this was called "Project Human Resource Management"
  7. Project Communications Management  : the processes that are required to ensure timely and appropriate planning, collection, creation, distribution, storage, retrieval, management, control, monitoring, and the ultimate disposition of project information.
  8. Project Risk Management  : the processes of conducting risk management planning, identification, analysis, response planning, and controlling risk on a project.
  9. Project Procurement Management  : the processes necessary to purchase or acquire products, services, or results needed from outside the project team. Processes in this area include Procurement Planning, Solicitation Planning, Solicitation, Source Selection, Contract Administration, and Contract Closeout.
  10. Project Stakeholder Engagement  : the processes required to identify all people or organizations impacted by the project, analyzing stakeholder expectations and impact on the project, and developing appropriate management strategies for effectively engaging stakeholders in project decisions and execution.

Each of the ten knowledge areas contains the processes that need to be accomplished within its discipline in order to achieve effective project management. Each of these processes also falls into one of the five process groups, creating a matrix structure such that every process can be related to one knowledge area and one process group.

Extensions

While the PMBOK Guide is meant to offer a general guide to manage most projects most of the time, there are currently three official extensions:

Criticism and alternatives

The PMBOK is a widely accepted standard in project management, however there are alternatives to the PMBOK standard, and PMBOK does have its critics. One thrust of critique has come from the critical chain developers and followers (e.g. Eliyahu M. Goldratt and Lawrence P. Leach), [10] as opposed to critical path method adherents. The PMBOK Guide section on Project Time Management does indicate Critical Chain as an alternative method to Critical Path.

A second strand of criticism originates in Lean Construction. This approach emphasises the lack of two way communication in the PMBOK model and offers an alternative which emphasises a language/action perspective and continual improvement in the planning process. [11]

See also

Related Research Articles

Earned value management (EVM), earned value project management, or earned value performance management (EVPM) is a project management technique for measuring project performance and progress in an objective manner.

Project management is the process of supervising the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet predefined objectives.

The Software Engineering Body of Knowledge refers to the collective knowledge, skills, techniques, methodologies, best practices, and experiences accumulated within the field of software engineering over time. A baseline for this body of knowledge is presented in the Guide to the Software Engineering Body of Knowledge, also known as the SWEBOK Guide, an ISO/IEC standard originally recognized as ISO/IEC TR 19759:2005 and later revised by ISO/IEC TR 19759:2015. The SWEBOK Guide serves as a compendium and guide to the body of knowledge that has been developing and evolving over the past decades.

<span class="mw-page-title-main">Work breakdown structure</span> A deliverable-orientated breakdown of a project into smaller components.

A work-breakdown structure (WBS) in project management and systems engineering is a deliverable-oriented breakdown of a project into smaller components. A work breakdown structure is a key project management element that organizes the team's work into manageable sections. The Project Management Body of Knowledge defines the work-breakdown structure as a "hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables."

A project plan, according to the Project Management Body of Knowledge (PMBOK), is: "...a formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among project stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be sumarized or detailed."

<span class="mw-page-title-main">Project manager</span> Professional in the field of project management

A project manager is a professional in the field of project management. Project managers have the responsibility of the planning, procurement and execution of a project, in any undertaking that has a defined scope, defined start and a defined finish; regardless of industry. Project managers are first point of contact for any issues or discrepancies arising from within the heads of various departments in an organization before the problem escalates to higher authorities, as project representative.

ISO/IEC/IEEE 12207Systems and software engineering – Software life cycle processes is an international standard for software lifecycle processes. First introduced in 1995, it aims to be a primary standard that defines all the processes required for developing and maintaining software systems, including the outcomes and/or activities of each process.

The Project Management Institute is a U.S.-based not-for-profit professional organization for project management.

Project stakeholders are persons or entities who have an interest in a given project. According to the Project Management Institute (PMI), the term project stakeholder refers to "an individual, group, or organization, who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio. ISO 21500 uses a similar definition.

In organizational studies, resource management is the efficient and effective development of an organization's resources when they are needed. Such resources may include the financial resources, inventory, human skills, production resources, or information technology (IT) and natural resources.

Project Management Professional (PMP) is an internationally recognized professional designation offered by the Project Management Institute (PMI). As of 31 July 2020, there are 1,036,368 active PMP-certified individuals and 314 chartered chapters across 214 countries and territories worldwide.

A project management office is a group or department within a business, government agency, or enterprise that defines and maintains standards for project management within the organization. The PMO strives to standardize and introduce economies of repetition in the execution of projects. The PMO is the source of documentation, guidance, and metrics on the practice of project management and execution.

PMHUB is a free virtual community of professional project managers who recognise the Project Management Institute's Project Management Body of Knowledge project management standard. Whilst a number of the members have already earned their PMP certification the majority of the community consists of those who aspire to become PMP or CAPM-certified.

Software Quality Management (SQM) is a management process that aims to develop and manage the quality of software in such a way so as to best ensure that the product meets the quality standards expected by the customer while also meeting any necessary regulatory and developer requirements, if any. Software quality managers require software to be tested before it is released to the market, and they do this using a cyclical process-based quality assessment in order to reveal and fix bugs before release. Their job is not only to ensure their software is in good shape for the consumer but also to encourage a culture of quality throughout the enterprise.

A glossary of terms relating to project management and consulting.

Extreme project management (XPM) refers to a method of managing very complex and very uncertain projects.

Within project management, risk management refers to activities for minimizing project risks, and thereby ensuring that a project is completed within time and budget, as well as fulfilling its goals.

The following outline is provided as an overview of and topical guide to project management:

ISO 21500, Guidance on Project Management, is an international standard developed by the International Organization for Standardization, or ISO starting in 2007 and released in 2012. It was intended to provide generic guidance, explain core principles and what constitutes good practice in project management. The ISO technical committee dealing with project management, ISO/PC 236 was held by the American National Standards Institute (ANSI) which had approved four standards that used Project Management Institute (PMI) materials, one of which was ANSI/PMI 99-001-2008, A Guide to the Project Management Body of Knowledge - 4th Edition.

In project management, resource smoothing is defined by A Guide to the Project Management Body of Knowledge as a "resource optimization technique in which free and total float are used without affecting the critical path" of a project. Resource smoothing as a resource optimization technique has only been introduced in the Sixth Edition of the PMBOK Guide and did not exist in its previous revisions. It is posed as an alternative and a distinct resource optimization technique beside resource leveling.

References

  1. ↑ IEEE (2011), IEEE Guide--Adoption of the Project Management Institute (PMI(R)) Standard A Guide to the Project Management Body of Knowledge (PMBOK(R) Guide)--Fourth Edition, archived from the original on July 17, 2012
  2. ↑ "A GUIDE TO THE PROJECT MANAGEMENT BODY OF KNOWLEDGE" (PDF). Archived from the original (PDF) on 2020-07-01. Retrieved 2020-06-29.
  3. ↑ "A Guide to the Project Management Body of Knowledge (PMBOK Guide) 2000 Edition" (PDF). Retrieved 2020-06-29.
  4. 1 2 A Guide to the Project Management Body of Knowledge, copyright page, edition 2 ISBN   1-880410-12-5, and edition 3 2004 ISBN   978-1-930699-45-8, and edition 4 2008 ISBN   1-933890-51-7
  5. ↑ "A Guide to the Project Management Body of Knowledge Third Edition" (PDF). Retrieved 2020-06-29.
  6. ↑ "A Guide to the Project Management Body of Knowledge (PMBOK Guide) Fifth Edition" (PDF). Retrieved 2020-06-29.
  7. ↑ "PMBOK® Guide 6th Edition will be released on 6th of September 2017 - everything you need to know about the new PMBoK guide Edition and the related exam changes!!". pmplus - the blog. 2017-06-16. Retrieved 2020-03-27.
  8. ↑ Guillen, Giovanny (2021-10-19). "The PMBOK guide® – Seventh Edition Summary". Project Management Times. Retrieved 2022-03-07.
  9. 1 2 Project Management Institute, A Guide to the Project Management Body of Knowledge – Fifth Edition, Project Management Institute Inc., 2013, Page 2.
  10. ↑ Eliyahu M. Goldratt . ISBN   0884271536 and Lawrence P. Leach. (Artech House Professional Development Library). ISBN   1580530745
  11. ↑ Koskela, L. & Howell, G. (2002) 'The underlying theory of project management is obsolete', Proceedings of the PMI Research Conference 2002, 293-302.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.