Sometimes I hear people saying they're going to use the "PMBoK methodology" to drive some project. One of this days I saw a controversy about an article at iMasters (brazillian web-related e-magazine) where the author was criticizing agile methodologies, and in the comments section that also was repeated.
I think it's worth to clarify: PMBoK is not a project management methodology, in fact, the acronym stands for Project Management Book of Knowledge, which describes a common vocabulary in the knowledge areas related to project management.
Putting it simple, nothing stops you from using what is described in PMBoK to manage a Scum or eXtreme Programming project the same way that nothing stops you from managing a non-agile project and still being far from PMBoK recomendations.
The greatest value of PMBoK, to me, is to stablish the 8 axes that any project manager (in any area) should pay attention for. The axes are:
- Human Resources
The book itself says that it's up to the project manager to define how much each of this axes are relevant to the success of the project. The same way, despite PMBoK describing a set of processes in each of the axes and each of the phases of the project management, that processess have a role of equalizing the "language" for the project managers, since it lists almost all the possible procedures in project management. It's up, again, to the managr to decide which one will generate value to the project
In summary: methodolodies are always specific to the theme, and to clarify, the curring line, imho, for agile vs non-agile methodologies is in the previous definition of scope vs the definition of a floating scope where some small part of the software already generates a lot of value. If you say your're using agile and your project doesn'g fit here, you're just butying your head in the sand..