We are starting work on the updates to our training courses (for the change dates see: Examination Updates) and rather like most of the enhancements in the 5th Edition (due for publication on 31st December). Over the next few months we will be posting a number of commentaries on the changes and improvements. This post looks at some of the key changes.
The new PMBOK® guide now has 47 processes (up from 42) and a new Knowledge Area:
Four planning processes have been added: Plan Scope Management (back from the 3rd Edition), Plan Schedule Management, Plan Cost Management, and Plan Stakeholder Management. This change provides clearer guidance for the concept that each major Knowledge Area has a need for the project team to actively think through how the related processes will be planned and managed, and that each of the subsidiary plans are integrated through the overall project management plan, which is the major planning document for guiding further project planning and execution.
The addition of a new knowledge area called ‘Stakeholder Management’ has been created making 10 Knowledge areas. In keeping with the evolution of thinking regarding stakeholder management within projects, this new Knowledge Area has been added addressing Project Stakeholder Management. Information on stakeholder identification and managing stakeholder expectations has been moved from Project Communications Management to this new Knowledge Area to expand upon and increase the focus on the importance of appropriately engaging project stakeholders in the key decisions and activities associated with the project. New processes were added for Plan Stakeholder Management and Control Stakeholder Engagement. We will be discussing this important initiative in later posts.
Data flows and knowledge management concepts have been enhanced:
The PMBOK® Guide now conforms to the DIKW (data, information, knowledge, wisdom) model used in the field of Knowledge Management. Information/Data is segregated into three phases:
Work Performance Data. The raw observations and measurements identified during the performance of the project work, such as measuring the percent of work physically completed.
Work Performance Information. The results from the analysis of the performance data, integrated across areas such as the implementation status of change requests, or forecasts to complete.
Work Performance Reports. The physical or electronic representation of work performance information compiled in project documents, intended to generate decisions, actions, or awareness.
Understanding the information in the reports and making wise decisions are functions of the competence of the individual manager reading the report and are therefore beyond the scope of a process (for more on effective communication visit our PM Knowledge Index )
Annex A1 – The Standard for Project Management of a Project created.
This new annex has been designed to serve as a standalone document. This positions the Standard for Project Management away from the main body of the PMBOK® Guide material allowing the evolution of the Body of Knowledge material to be separated from the actual Standard for Project Management. Chapter 3 remains as the bridge between Sections 1 and 2 and the Knowledge Area sections and introduces the project management processes and Process Groups as in the previous editions of the PMBOK® Guide.
More on the improvements next time – in the interim, from now onward our daily question will be Tweeted with reference to both the 4th and the 5th Editions of the PMBOK® Guide: see today’s question.
Pat Weaver
Lynda Bourne
Aavssitedev's Blog
Hi,
I am pleased to see that the gap in Stakeholder Management is being corrected. However, I don’t see anything above that rectifies the lack of a process to deal with closing HR. PMBOK has a process for closing Procurement, but not an equivalent process for releasing staff and contractors that have been engaged via the “Acquire Project Team” process. Surely we should have a process that talks about disengaging staff – giving them and their managers feedback on their performance, etc…?
Thanks,
Colin
Pingback: PMBOK® Guide 5th Edition now in stock | Aavssitedev’s Blog
HI.
I am Japanease, so ,I not reads PMBOK 5Th Data flow diagram.
The data flow diagram of pmbok5, whether it is easy to understand?
—————————————————–
I rewrote the data flow of the “A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) – Fourth Edition”
At My Data flow diagram,
– It includes all the processes on a single page.
– the LINK that Fording information are noted by top to bottom,or,left to right.
the LINK that feedback (or change request) information are noted by right to left.
– Input / output that can distinguish between the project management plan and project documentation.
and hat can distinguish between create documentation and update documentation.
-The color of the line of that link, you can distinguish between optional information that is fed back, and the information is forwarded.
-To that node, so that the process to fill the number, even if you can not read Japanese, You will be able to overview.
————————————————————
I make it easier to understand some of the problems.
— \8.2 process outputs “training plan”,and it is input by \9.3,and is rated by \9.4.
–\9.4 process outputs ” issue log”,and it input by \10.4.
— \10.4 process is most lower right corner.
There in its place is GOAL (“\10.4 satisfaction of Stakeholder “).
——————————————————————–
best reguard.
The 4th Edition of the PMBOK is now out of date and has little relevance.
I am try to writes “PMBOK fifth edition Data flow diagram”.
“DIKW model”, there was a significant impact on ”PMBOK 5th Data flow”.
” issue log” had been organized on PMBOK5.