Project Management Body of Knowledge
Body of knowledge for project management From Wikipedia, the free encyclopedia
Body of knowledge for project management From Wikipedia, the free encyclopedia
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.
Author | Project Management Institute |
---|---|
Genre | Business |
Published | 2021 (Project Management Institute) |
Pages | 370 (seventh edition) |
ISBN | 978-1-62825-664-2 |
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.
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.
Year | Title | Revision summary |
---|---|---|
1996 | PMBOK Guide | Published 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] |
2000 | PMBOK Guide, 2000 Edition | The second edition (published as the 2000 Edition) added new material reflecting the growth of practices.[3][4] |
2004 | PMBOK Guide, Third Edition | The 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] |
2008 | PMBOK Guide, Fourth Edition[4] | |
2013 | PMBOK Guide, Fifth Edition[6] | |
2017 | PMBOK Guide, Sixth Edition | The sixth edition (September 2017) added several topics and included agile practices for the first time.[7] |
2021 | PMBOK Guide, Seventh Edition | The seventh edition (2021) presents major structural changes, such as replacing the 10 knowledge areas with 12 principles and including agile practices more comprehensively.[8] |
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"
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.
The five process groups are:
The ten knowledge areas, each of which contains some or all of the project management processes, are:
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.
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:
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]
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.