by Lynda Bourne
In my last post—It’s Time for a Long, Hard Look at Processes—I questioned if A Guide to the Project Management Body of Knowledge (PMBOK® Guide) should be updated every four years, or if it should become a dynamic knowledge management system similar to Wikipedia. The post generated a number of comments, which I’m going to try to address now.
The fundamental purpose of a standard is to offer standardized advice organizations can rely on. Standards are frequently referenced in contracts and other formal documentation, and they form the basis for certifications. The PMBOK® Guide fulfills all of these purposes. In this situation, stability is essential. Globally, standards are reviewed and updated every four to five years to balance the need for currency against the need for consistency.
The PMI Registered Education Provider (R.E.P.) community has a busy few months each time the PMBOK® Guide is updated, requiring them to go through their training materials to bring them all up to date. This is magnified many times over as organizations around the world update their documentation to align with the new standard.
But the American National Standards Institute (ANSI) standard is only one part of the PMBOK® Guide. The guidance part is the larger aspect of the book and also, in my opinion, the most useful. This element is a knowledge repository and if access to validated information is readily available, knowledge management systems should seek to be as up to date as possible. To achieve this, most knowledge management systems are web-based and assume that once information is printed, it is no longer current. Managing a knowledge management system needs skill and knowledge but should be a real-time, full-time function.
Given this, I suggest that PMI separate the standard part of the document from the knowledge element. The standard section would consist of the ANSI Standard (part two of the current PMBOK® Guide) and the supporting core knowledge that does not change much. This standard and supporting information would remain on the four- to five-year update cycle. The resulting document would be much thinner than the current PMBOK® Guide.
The knowledge element builds onto this as a cloud-based resource and should be the subject of continual improvement and updating. Allowing PMI members to contribute their knowledge on a continuous basis, subject to review and edit, would allow the body of knowledge to grow and adapt as project management grows and adapts.
A careful design of the knowledge structure based on the PMBOK® Guide—augmented with information from the other standards published by PMI and enhanced with current developments from industry—would create a very useful and dynamic source of knowledge for the global project management community.
If access to this project management knowledge bank is free to members and available for a fee to commercial users and non-members, the value of membership would be enhanced and PMI would be positioned to maintain its position as a global leader in the development of project management.
It’s an interesting challenge. What do you think?