Archive for the ‘PMI’ Category

PMI’s PMBOK 5th Edition Project Management VS Operations Management

Project Management is not the same as Operations Management. They’re quite different.

Project Management is temporary having a beginning and end, while Operations Management is permanent, continuous.

The goal of PM is to create unique products, services or results. The goal of OM is to produce a repetitive product or service.

A product in PM (a new electric car) is not the same as a product in OM (mass production of that new electric car).


PMI’s PMBOK 5th Edition 10 Knowledge Areas

The PMI’s PMBOK 5th Edition 10 Knowledge Areas are:

  1. Integration Management
  2. Scope Management
  3. Time Management
  4. Cost Management
  5. Quality Management
  6. Human Resources Management
  7. Communications Management
  8. Risks Management
  9. Stakeholders Management
  10. Procurement Management

There are different activities within each process, each one having their own inputs, outputs, tools and techniques.

An Introduction to PMBOK Guide 5th Edition: Knowledge Areas, Processes and Process Groups

100+ Tips on PMP Certification Training & Study by 100 PMPs

My Journey to Earning the PMP Certification

PMI’s PMBOK 5th Edition 5 Processes Groups

The PMI’s PMBOK 5 Processes Groups are:

  1. Initiation
  2. Planning
  3. Execution
  4. Monitoring and Controlling
  5. Closing

They are supposed to follow the natural flow of activities done througout a project life cycle.

Project Definition according to the PMI’s PMBOK 5th Edition

The PMI’s PMBOK defines a project as:

a temporary endeavor, with a beginning and an end, undertaken to create a unique product, service or result.

The project ends when the goals are achieved (the product, service or result is completed), when the goals cannot be achieved or they are not needed anymore.

To create the project’s product, service or result, we need to perform a series of activities, grouped into 47 processes. Each process has its own inputs, techniques, tools and outputs. These 47 processes are grouped into 5 process groups:

  1. Initiation
  2. Planning
  3. Execution
  4. Monitoring and Controlling
  5. Closing

These 5 process groups are listed in a logical order as per the project’s phases.

Also, the 47 processes are grouped into 10 knowledge areas:

  1. Integration
  2. Scope
  3. Time
  4. Cost
  5. Quality
  6. Human Resources
  7. Communications
  8. Risks
  9. Procurement
  10. Stakeholder

So this means that each one of the 47 processes belongs to only one process group and only one knowledge area simultaneously.

Given that I’ve worked in the software industry for 8 years and I’m familiar with software development lifecyles, I would compare the PMI’s PMBOK process groups and knowledge areas with the Unified Process’ phases and disciplines. For more about this comparison, I’d recommned the following article: Standards, compliance, and Rational Unified Process, Part I: Integrating RUP and the PMBOK

In the software industry, a typical project goal is to create a new information system for a customer. Depending on the requirements complexity the information system must cover, it may take up to 6, 12, 36 or more months to be completed. Usually, the requirements may have changed by them or the customer may not need it anymore. Also, a “test period” is very commong in the software industry. We usually build information systems for our customers as the end result of a project. Given the complexity of software systems, testing is very important and a testing the system in the real world for, let’s say 3 months after “project closing”.