1) The 4th edition of the PMBOK Guide consolidates and clarifies concepts from the 3rd edition. It includes 2 new processes and removes 2 processes while combining 4 processes into 2.
2) There are now 42 processes total, written in a verb-noun format for improved readability. The processes have been reorganized for better alignment with how projects are performed.
3) Additional information is provided on portfolio, program, and project management differences as well as on interpersonal skills.
Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
White paper changes to the pmbok 4th edition
1. White Paper on
A Project Manager’s Perspective on Changes to the Guide to the Project Management
Body of Knowledge (PMBOK® Guide) Fourth Edition
Erika Flora, MS, PMP, ITIL Expert - Principal Consultant, Beyond20, erika.flora@Beyond20.com
I. INTRODUCTION
On December 31, 2008, the Project Management Institute (PMI®) released the 4 th edition of the
PMBOK® Guide, the foundational book used to study and prepare for the Project Management
Professional (PMP) exam. On July 1, 2009 the exam changed over to the 4th edition, and project
management professionals world-wide now use this new edition to prepare for the PMP exam. So,
what has changed? The good news is that many of the core concepts and order of project activities
performed are the same as in the 3rd edition. If you took and passed the 3rd edition exam, what
you have learned is still valid. If you have studied the 3rd edition material, but have not yet taken
the exam, you will, unfortunately, have a lot of process Inputs, Outputs, Tools & Techniques to re-
learn and memorize.
Overall, the refresh of the new text mainly consolidates and clarifies previously confusing concepts
and includes additional concepts that today’s Project Manager deals with. This white paper
outlines these changes, in chronological fashion and in line with how projects are actually being
performed (i.e. in order of each of the five process groups - Initiating, Planning, Executing,
Monitoring and Controlling, and Closing). Thus, it takes a slightly different slant from other white
papers on the subject. For a list of changes according to each of the nine Knowledge Areas, see the
Preface to and Appendix A of the Fourth Edition in the PMBOK® Guide (pages XXII-XXIII and 349-
357).
II. OVERVIEW OF CHANGES
General
The two prevailing themes with the PMBOK® Guide 4th edition changes are that of “clarity” and
“consistency”. In teaching 3rd edition classes, students in every class always had some confusion
around conflicting definitions and have lots of questions around why some documents are
mentioned and why others weren’t as an Process Inputs, Outputs, Tools or Techniques. The 4 th
edition seems to do a good job of addressing and alleviating these types of issues.
Project Management Processes
First, there are now 42 processes detailed in the fourth edition of the PMBOK® Guide, as compared
to 44 processes in the 3rd edition. Two new processes have been added, two have been removed,
and four other processes have been combined into two, specifically within Project Procurement
Management, as detailed below:
New Removed Consolidated
Identify Stakeholders Develop Preliminary Plan Purchases and Acquisitions and
Collect Requirements Scope Statement Plan Contracting > Plan Procurements
Scope Planning Request Seller Responses and Select
Sellers > Conduct Procurements
Page 1 of 21
www.Beyond20.com
2. A few other processes have changed process groups, for example, “Manage Project Team” is now
an Executing process; and “Manage Stakeholders” is now a Monitoring and Controlling process.
Also, to improve readability and consistency throughout, all 42 processes are now in verb-noun
format. For example, “Scope Definition” has been renamed as “Define Scope”. Since Project
Managers are performing these activities within their projects, it makes sense that the processes
would be written this way. For those of us used to the process names as they are written in the 3 rd
edition, it takes a little practice to get the names straight in the 4 th edition. However, long term,
this is a much more intuitive way to refer to the processes we perform.
Portfolio, Program, and Project Management
In chapter 1 of the PMBOK® Guide 4th edition, there is additional information on the differences
between managing a Portfolio, Program, and Project as many project managers are now finding
themselves managing programs and even portfolios; and it is important to understand and be able
to communicate the differences between them. I find this is a common question from team
members and other non-Project Managers in many organizations.
Enterprise Environmental Factors and Organizational Process Assets
Further, there is a clearer differentiation between Enterprise Environmental Factors (EEFs) and
Organizational Process Assets (OPAs). These are detailed in the table below. Also, EEFs and OPAs
serve as inputs (and outputs) to more processes in the 4th edition and closer line up with real life.
Enterprise Environmental Factors Organizational Process Assets
Any or all external environmental factors Any or all process related assets, from
and internal organizational environmental any or all of the organizations involved in
factors that surround or influence the the project that are or can be used to
project’s success. These factors are from influence the project’s success. These
any or all of the enterprises involved in the process assets include formal and
project, and include organizational culture informal plans, policies, procedures, and
and structure, infrastructure, existing guidelines. The process assets also
resources, commercial databases, market include the organizations’ knowledge
conditions, and project management bases such as lessons learned and
software. historical information.
Project Initiation and Planning documents
There have been some changes involving the Project Management Plan, Project Charter, and
Project Scope Statement. Namely, the Project Management Plan and its subsidiary plans have
been more clearly defined and separated out. There has also been a clearer distinction between
plans and other Project documents (see page 350 in the PMBOK® Guide for a list of these items). In
addition, there is a clearer distinction between the components of the Project Charter and the
Project Scope Statement (the Preliminary Project Scope Statement has gone away). The
differences are detailed on page 351 of the PMBOK® Guide 4th edition.
Requested Changes, Corrective and Preventive Actions (CAPA), and Defect Repairs
Whereas, these items were separated in the 3rd edition, these have all been consolidated under the
heading of “Change Requests”. Rather, the PMBOK® Guide defines different types of requests.
Page 2 of 21
www.Beyond20.com