Project Management Body of Knowledge: Difference between revisions

Revision as of 11:07, 20 June 2022

Latest revision as of 10:54, 21 August 2025

(17 intermediate revisions by 13 users not shown)

Line 1:

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

{{Software development process}}

{{Infobox book

Line 30 ⟶ 31:

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

Line 69 ⟶ 70:

== 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 97 ⟶ 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.{{cn|date=March 2020}}

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

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

Line 117 ⟶ 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 132 ⟶ 133:

== External links ==

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

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

* [http://www.risk-services.com/DoDExtPMBOKJune2003.pdf US DoD extension to PMBOK Guide (PDF)]

{{Authority control}}

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