Using the PMBOK Guide to build

a practical PM process*
Key points
• PMBOK makes the task of defining a practical
and effective PM process easier if the PMBOK
standard is used appropriately.

• The current PMBOK guide offers a wealth of

detailed PM knowledge but its complexity can
be an obstacle in defining a PM process in a
simple, straightforward manner.
 PMBOK strengths
• High quality content focusing on essential PM
knowledge and processes recognized as good
practices.

• Defining and describing proven skills, tools

and techniques to deliver acceptable and
consistent project results.

• Uses a common PM language and approach.

 Challenges of PMBOK
• Learning Tree (LT) defines a PM process as
who does what activity when, whereas
PMBOK focuses in providing details and
options for doing a specific thing.

• There is a lack of milestone and gate-driven

control points.
• When using PMBOK guide processes you
should fit them into your project and your
organization.

• Avoid the temptation to simply apply a

standard view of PM to define a process,
because the processes may exceed your
requirements and be at odds with the people
and projects in your organization.
• A PM process is not simply a template or
checklist. It is a set of activities and steps to be
done in order to achieve a result.

• The template collects and documents results.

• The checklist provides the steps in the order

they need to be accomplished.
Three steps for practical application of
the PMBOK guide
• Define major gates across the project life cycle. In
other words build a gate driven road map.

• Prioritize and select a core set of processes and

related activities. Most PM processes work better
the simpler they are. Processes should be easy to
understand and easy to use.

• Add the supporting details that fully document and

explain activities in the road map. (guidelines,
roles, checklists, templates, deliverables, etc)