Overview of the Changes to the Project Management Processes
Project Integration Management –
“Manage Project Knowledge” is introduced in “Executing” process group together with “Direct and Manage Project Work”
this new process emphasizes continuous learning during the execution of the project and the knowledge gained can be used as a feedback to better the project
Lessons Learned Register is an important output of the “Manage Project Knowledge” process
Project Scope Management – both Project Management and Business Analysis are emphasized as they work together to achieve the best project goals
Project Schedule Management –
Project Time Management is now renamed as Project Schedule Management as a correction to the wrong terminology used in PMBOK® Guide 5th Edition — that only schedule can be managed, not time
“Estimate Activity Resources” Process is removed from Project Schedule Management to Project Resource Management
Project Cost Management – Not much changes
Project Quality Management –
“Perform Quality Assurance” process is renamed as “Manage Quality” which is a much more commonly used terms in quality management world
Project Resource Management –
Project Human Resources Management is now renamed as Project Resource Management, which covers a much broader scope of both team resources (i.e. human members) and physical resources (such as equipment, computing machines, etc.)
“Estimate Activity Resources” Process is relocated here
“Control Resources” process is newly added to the “Executing” process group to address the allocation and provision of the resources as planned and monitoring of physical resources vs planned
Project Communications Management – Not much changes
Project Risk Management –
“Implement Risk Responses” is newly added Executing process group which is the process of implementing agreed-upon risk response plan in order to address project risks (this is a logical addition as in the 5th edition there is not a process to actually carry out the risk responses)
“Control Risks” process is renamed as “Monitor Risks” — a sensible change of terminology
There are now 5 Risk Response Strategies for threats: Escalate (newly added), Avoid, Transfer, Mitigate & Accept and 5 Risk Response Strategies for opportunities: Escalate (newly added), Exploit, Share, Enhance & Accept
Project Procurement Management –
“Close Procurements” process is now removed as while Project Managers can support procurement closures, they are usually not given the authority to close the contract.
Project Stakeholder Management – Not much changes Saving Changes...
That's a long list! My favorite is they added "Escalate". Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Thanks for the assessment. It's good that KM is now explicitly added to the puzzle. Though, we know it is all inclusive, not just during execution. Saving Changes...
Mahabubur RahmanProject Manager Structures-Bridges| Department of Infrastructure, Government of Nothwest TerritoriesYellowknife, Northwest Territories, Canada
Good information Kevin. I think, this is one of the main areas (table) where change will take place with every upcoming edition of the PMBOK! Saving Changes...
Thanks Kevin for sharing the changes incorporated at process level in latest edition to Guide to PMBOK. However, these are just the tip of ice berg there are many more changes to the ITTOs in each process. Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
Thanks for sharing the changes, Drake. Saving Changes...
Vijay SelvarajLead Engineer| W-IndustriesHouston TX, United States
Found one more thing
Scope Baseline we now have two additional components Planning Package & Work Package in addition to Project Scope Statement, WBS & WBS dictionary... Saving Changes...
