USA/Canada: 866.259.2454 | International: +1.418.907.5184

PMBOK 4th edition: the human at the center

I recently had the chance to sit it on a very informative presentation about the changes to the PMI’s Project Management Body of Knowledge 4th edition, aka the PMBOK. It’s important to stay up-to-date on profesionnal best practices, and there’s been a lot of discussion on the new PMBOK.

I’ll spare you the details of the new processes and the deleted processes in the system. I’ll spare you the details of the new flowcharts.

Here’s what stuck my about the changes in the new PMBOK: it put more emphasis on the human side of project management. Managing stakeholders is more important.

There’s even a whole section about interpersonal skills, Appendix G, which talks about leadership, team building, motivation, communication, and so on.

“Respect and trust, rather than fear and submission, are the key elements of effective leadership.” – PMBOK 4 th edition, page 448.

I believe it’s the first time the PMI takes a real stance about management styles and personal interaction.

It was not a minute too soon.

By |2009-06-24T11:50:00-04:002009-06-24|

Get over the PMBOK

Since it’s Canadian Project Management week, I thought I would start the week with a PMI-related post.

When I happen to discuss the PMI project management method, I often hear the comment that the PMI’s method is too heavy and creates too much red tape. The Project Management Book of Knowledge (PMBOK) is pointed as the big culprit.

Truth is, the PMI and its PMBOK a misunderstood.

Time and time again, the PMI stresses that the PMBOK is a collection of best practices in project management. It’s not a set of regulations. It’s not a list of obligations. It is simply a repository of information for project management.

The PMI does not expect small projects to go through all 50-some processes. That would turn a 6-week project into a 12-week project. In fact, the PMI states:

“The PMBOK Guide identifies that subset of the project management body of knowledge generally recognized as good practice. […] Good practice does not mean the knowledge described should always be applied uniformly to all projects; the organization and/or management team is […]

By |2009-04-20T14:34:00-04:002009-04-20|
Go to Top