Skip to main content

Project Management Dynamics: Ten Knowledge Areas

Project Management Body of Knowledge

Ten Knowledge Areas

Ten knowledge areas:

Project integration management – Activities are added related to managing the knowledge that is generated during the project. This includes lessons learned and other artifacts. Better management of this activity can help disseminate the knowledge to project teams more effectively increasing productivity.

Project Scope Management – Relationship and interactions between project managers and business analysts in managing and controlling scope.

Perform Quality Assurance – This knowledge area has been replaced with “Manage Quality”. This is because in many organizations, quality is managed outside the project. So, this ensures that even in those cases, the project managers are always managing quality in their projects.

• There are some sections and knowledge areas that have been renamed. More specifically, “Project Time Management” has been replaced with “Project Schedule Management” because in reality that’s what that knowledge area is about, which is to manage the schedule of the project and not to manage time.

• The second knowledge area that has been renamed is “Project Human Resources Management”. This is because each project has other resources other than “human resources” that have to be managed as well. Therefore, this knowledge area has been renamed to “Project Resources Management.”

• Knowledge area related to “Project Communications Management” hasn’t been changed much in the sixth edition of the PMBOK guide but more clarity has been provided related to “communication” and “communications” and how they are different and impact the overall project communications.

• In Project Risk Management a number of changes have been introduced. The important change has been that this section now addresses the overall project risk and not just “event driven” risk. Also, in project risk management, an “escalate” function has been added to enable risks to be escalated to program and portfolio levels, especially when projects are part of programs and portfolios.

• The “Project Procurement” knowledge area has been redone to make the focus more international based to account for worldwide procurement.

Project Stakeholder Management – similar to program management, the knowledge area has been renamed to “Project Stakeholder Engagement”as that’s what a project manager usually does, which is to engage with project stakeholders rather than manager stakeholders. Stakeholders can come from all parts of the organization and external to the organization and they can’t be “managed” in the traditional sense. The correct way is to engage with them and to have a plan to engage with them.

 

 

Reference Librarian

Elia Trucks's picture
Elia Trucks
Contact:
Anderson Academic Commons
2150 E. Evans Ave.
Denver, CO 80208
303-871-3480