Project Management Body of Knowledge: Difference between revisions

Revision as of 09:22, 24 January 2020

Latest revision as of 10:54, 21 August 2025

(45 intermediate revisions by 34 users not shown)

Line 1:

{{Short description|Body of knowledge for project management}}

{{Software development process}}

{{Infobox book

Line 7 ⟶ 8:

| country =

| genre = Business

| published = 20172021 ([[Project Management Institute]])

| isbn = 978-1-62825-184664-52

| title_orig =

| translator =

| image = File:PMBOK.jpg

| caption = First edition

| illustrator =

| cover_artist =

Line 18 ⟶ 19:

| subject =

| media_type =

| pages = 592370 ''(sixthseventh edition)''

| dewey =

| congress =

Line 24 ⟶ 25:

}}

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'' (the ''PMBOK Guide to the PMBOK'' or the Guide), a book whose sixthseventh edition was released in 20172021. The Guide is aThis document resultingresults from work overseen by the [[Project Management Institute]] (PMI), which offers the [[Certified Associate in Project Management|CAPM]] and [[Project Management Professional|PMP]] certifications.

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-20111490–2011).<ref>{{citation |url=http://ieeexplore.ieee.org/servlet/opac?punumber=6086683 |archive-url=https://archive.today/20120717053622/http://ieeexplore.ieee.org/servlet/opac?punumber=6086683 |url-status=dead |archive-date=July 17, 2012 |title=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 |author=IEEE |year=2011}}</ref>

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

The evolution of the ''PMBOK Guide'' is reflected in editions of the Guide. The Guide was first published by the [[Project Management Institute]] (PMI) in 1996. That document was to some extent based on earlier work that began with a [[white paper]] published in 1983 called the "Ethics, Standards, and Accreditation Committee Final Report." The second edition was published in 2000.<ref>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}}</ref>

{| class="wikitable"

|+

In 2004, the ''PMBOK Guide — Third Edition'' was published with major changes from the previous editions. The ''Fourth edition'' was published in 2008. The ''Fifth Edition'' was released in 2013.

!Year

!Title

The latest English-language version of ''The PMBOK Guide — The Sixth Edition was released in September 2017.<ref>[https://www.pmi.org/certifications/types/project-management-pmp/update] Project Management Institute], retrieved 11 July 2017</ref>''

!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.<ref>{{cite web |title=A GUIDE TO THE PROJECT MANAGEMENT BODY OF KNOWLEDGE |url=http://itq.ch/pdf/pmbok1.pdf |archive-url=https://web.archive.org/web/20200701142517/http://itq.ch/pdf/pmbok1.pdf |archive-date=2020-07-01 |access-date=2020-06-29}}</ref>

|-

|2000

|''PMBOK Guide, 2000 Edition''

|The second edition (published as the ''2000 Edition'') added new material reflecting the growth of practices.<ref>{{cite web |title=A Guide to the Project Management Body of Knowledge (PMBOK Guide) 2000 Edition |url=http://www.cs.bilkent.edu.tr/~cagatay/cs413/PMBOK.pdf |access-date=2020-06-29}}</ref><ref name=":0">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}}</ref>

|-

|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".<ref>{{Cite web |title=A Guide to the Project Management Body of Knowledge Third Edition |url=http://www.physics.rutgers.edu/~ransome/muse/project/reference/PMBOK3rdEnglish.pdf |access-date=2020-06-29}}</ref>

|-

|2008

|''PMBOK Guide, Fourth Edition''<ref name=":0" />

|

|-

|2013

|''PMBOK Guide, Fifth Edition<ref>{{cite web |title=A Guide to the Project Management Body of Knowledge (PMBOK Guide) Fifth Edition |url=http://www.orange.ngo/wp-content/uploads/2016/09/PMBOK-Guide-5th-Edition-PMI.pdf |access-date=2020-06-29}}</ref>''

|

|-

|2017

|''PMBOK Guide, Sixth Edition''

|The sixth edition (September 2017) added several topics and included [[Agile software development|agile practices]] for the first time''.''<ref>{{Cite web |date=2017-06-16 |title=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!! |url=https://projectmanagement.plus/new-pmbok-guide-6th-edition-and-pmp-exam-change-everything-you-need-to-know |access-date=2020-03-27 |website=pmplus - the blog |language=en-US}}</ref>

|-

|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.<ref>{{Cite web |last=Guillen |first=Giovanny |date=2021-10-19 |title=The PMBOK guide® – Seventh Edition Summary |url=https://www.projecttimes.com/articles/the-pmbok-guide-seventh-edition-summary/ |access-date=2022-03-07 |website=Project Management Times |language=en-US}}</ref>

|}

== 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."<ref name=PMBOK2012/> 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"

Line 67 ⟶ 98:

# [[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]].

# Project [[Scope (project management)|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.

# [[Project [[Schedule Management(project management)|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"

# [[Project cost management|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.

# 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.

Line 74 ⟶ 105:

# [[Project Risk Management]] : the processes of conducting risk management planning, identification, analysis, response planning, and controlling risk on a project.

# [[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.

# Project [[Stakeholder management|Stakeholder ManagementEngagement]] : 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.

Line 87 ⟶ 118:

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]]),<ref>[[Eliyahu M. Goldratt]] . {{ISBN|0884271536}} and Lawrence P. Leach. (Artech House Professional Development Library). {{ISBN|1580530745}}</ref> 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.<ref>Koskela, L. & Howell, G. (2002) 'The underlying theory of project management is obsolete', Proceedings of the PMI Research Conference 2002, 293-302. [https://usir.salford-repository.acworktribe.ukcom/9400output/11462587/2002_The_underlying_theory_of_project_management_is_obsolete.pdfthe-underlying-theory-of-project-management-is-obsolete]</ref>

==See also==

Line 95 ⟶ 126:

* [[Pmhub]]

* [[Project Management Professional|PMP]]

* [[PRINCE2]].

==References==

Line 101 ⟶ 132:

== External links ==

* [https://www.pmi.org/pmbok-guide-standards/foundational/pmbok PMBOK webpage] by the [[Project Management Institute]]

* [http://www.pmi.org/ PMI's website]

* [http://johnmuldoon.ie/wp-content/uploads/2014/08/PMBOK-Summarized.pdf PMBOK Summarized - A remarkbly concise guide to the PMBOK (PDF)]

{{Authority control}}

[[Category:1987 documents]]<!-- white paper -->

[[Category:1996 non-fiction books]]

[[Category:2013 non-fiction books]]

[[Category:2017 non-fiction books]]

[[Category:Project management]]