Glen Alleman shoots down some of the common misconceptions about the relationship between the PMBOK Guide and agile principles (here). As regular readers know, I’m sympathetic to agile approaches, I’ve found them very powerful in the right project context, and I push to incorporate agile principles further into our own content.
Of course, if I commented on Glen’s post itself, I’d be writing “ditto” or “I agree” a lot, so I’m just going to add on a bit:
- While many agile advocates over-read the PMBOK Guide, the guide did imply a waterfall approach, especially in earlier editions (Chapter 2). I can understand the confusion or over-reading.
- The pending 4th edition does have a more sophisticated treatment of project life cycles and explicitly addresses iterative relationships among project phases. It is hardly sufficient, but it is heading the right direction.
- PMI itself is quite eager to engage agile advocates for future editions (or extensions) of the PMBOK Guide. Several Global Corporate Council members were approached about how and whom to engage in the agile (or agile-savvy) community.
- My take is that creating an Agile extension to the PMBOK Guide would be the best initial approach. If nothing else, integrating agile-oriented PMs into the standard-setting process should be easier in an extension project.