How Scrum framework maps to PMBOK knowledge areas

I've been reading Ken Rubin's Essential Scrum. Because of this, I'm interested in understanding the consistencies and inconsistencies between the PMBOK standard and Agile techniques. An informative, though dated (2008) paper written by Peter Bennison provides an excellent starting point, based upon a reference project described by Bennison.

Benneson describes overlap between PMBOK processes and tools/techniquies and the Scrum framework used in the reference project, but the variance between the two approaches stands out to me. 

The greatest PMBOK overlap with Scrum identified by the author is in the Quality Management knowledge area. The methods employed during the reference project are instructive in understanding the strengths of Scrum:

1. Detailed acceptance criteria developed after every iteration [sprint] kickoff meeting
2. The client responsible for system testing after each iteration
3. Important features developed early, and thus subject to repeat testing (with each sprint)
 -Enabled through prioritized Product Backlog
4. First features developed were for release maintenance

In contrast, for the Scope Management knowledge area, Bennison emphasizes contrast between the PMBOK and the Scrum framework:  "The 'Tools' section of the Project Scope Management chapter leaves little doubt that scope is to be managed and controlled with centralized tools and decision making processes," while the Scrum-based reference project "used the product backlog and high-level acceptance criteria to prioritize and schedule feature development." The Work Breakdown Structure is also addressed in the paper. For the reference project, it's described as "based on features to be developed rather than tasks" - which, if you see the WBS as focused on deliverables, isn't that counterintuitive. 


No Comments

Add a Comment