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 responsible for determining what is appropriate for any given project.”
Source: A Guide to the Project Management Body of Knowledge (PMBOK Guide), Fourth Edition, page 4.
Project management is more than following rules blindly.
Project management is about knowing that to do for a specific project, team, stakeholder or sponsor. It’s about giving people the information they need, not the information we think they want. It’s about adjusting techniques and practices to our own organization, our own people, our own industry.
The PMBOK is there to provide a reference of common vocabulary and tools. It’s a source of inspiration. It’s a guide. It’s not an obligation.