PMBOK framework

From CEOpedia | Management online
Revision as of 21:14, 23 November 2020 by TomAlender (talk | contribs)

PMBOK means Project Management Body of Knowledge. The PMBOK is a guideline that is revised approximately all four years by the publisher, the Project Management Institute - PMI. The guide is closely linked to the American National Standard Institute called ANSI, which approved the PMBOK Guide as a offical standard in 1999 (Saladis, Kerzner 2011,p. 12). It is recognized worldwide as a reference and reference work for project management. The first edition of the PMBOK was published in 1996, the latest and currently valid 6th edition was published in September 2017. PMOK is characterized by the fact that the guideline is sector-neutral. In addition, PMOK is formulated in an industry- and method-independent way and can be applied to projects of any size and scope (Rodrigues 2001, p.1). It follows the idea that the project manager decides individually which contents from the PMBOK he wants to use for the concrete project. The work is structured in knowledge areas, process groups and processes as well as descriptions of inputs, outputs and suitable tools and methods (Saladis, Kerzner 2011,p. 13).

Fields of knowledge in the PMBOK

The following ten areas of knowledge exist:

  • Cost Management

The cost management has the task of estimating and budgeting the expenses for the project and explains how the project can be completed within the approved budget (Saladis, Kerzner 2011,p. 13).

  • Quality Management

The aim of this field of knowledge is to ensure that the quality requirements of the client are met or exceeded. To this end, Quality Management defines quality criteria, objectives and areas of responsibility (Saladis, Kerzner 2011,p. 13).

  • Resource Management

Identify, compile and control the resources required for the project. The goal is to have the right resources available at the right time. This makes it clear that, in addition to the project team, other resources are also necessary for successful project implementation (Saladis, Kerzner 2011,p. 13).

  • Integration Management

Integration management in projects involves the processes and procedures that combine the individual parts of the project into a whole. The goal of this field of knowledge is to coordinate the different project elements, phases and results in a holistic way in order to successfully complete the project. Thus it represents the main task of the project manager (Saladis, Kerzner 2011,p. 13).

  • Content and scope management

Scope management deals with the project product to be created and the general conditions: What exactly is done in this project and what is not, what do the work packages look like that create the deliverables and how is it ensured that exactly what is needed is done (Saladis, Kerzner 2011,p. 13).

  • Schedule management

Schedule Management deals with the scheduling of the project in order to ensure a timely completion. The duration and resource requirements of tasks are described and these are put into a schedule/sequence.

  • Risk Management

Das Risk Management beschreibt die Prozesse zur Identifizierung, Analyse und Bewertung von Risiken sowie zur Risikobehandlung und –verfolgung. Ziel des Risikomanagements ist die Erhöhung der Erfolgschancen des Projektes (Saladis, Kerzner 2011,p. 13).

  • Procurement Management
  • Stakeholder Management

All parties involved in the project and those interested in the project result are identified, and their needs and expectations are analyzed and documented. To ensure the success of the project, the stakeholders must be actively supported and their influence on the project must be managed and controlled (Saladis, Kerzner 2011,p. 13).

  • Communication Management

The task of communication management is to identify information needs, to set up an information and reporting system on the current status quo and the progress of the project, and to make the desired information available to the stakeholders (Saladis, Kerzner 2011,p. 13).

Process groups in the PMBOK

References

Author: Tom Alender