SCRUM vs. PMBOK. Which one is the best?

It’s common to hear that agile methodologies such as SCRUM are more practical and easy to apply than the PMBOK (A Guide to the Project Management Body of Knowledge, by the Project Management Institute). The most usual argument is that PMBOK is rigid and has little room for flexibility, and for that reason is not suited for most of today’s environments, which are complex and constantly subject to change. In this post I’d like to comment on the SCRUM vs. PMBOK debate.

First, SCRUM is undoubtedly the most popular agile methodology in use today. According to the official guide in Scrum.org, SCRUM is defined as:
 
“A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.”

SCRUM’s name comes from rugby, where a scrum is the formation the players take when restarting play, and involves players packing closely together with their heads down and attempting to gain possession of the ball. The analogy for this in a project is realized through creating a work environment where small teams share a common space. The speed and quality of their results will depend on the performance of their members and their direct communication and interaction.

The essence of SCRUM is the Sprint, a work period that lasts 1 to 4 weeks and produces as output a product increment that is demonstrable and usable. A SCRUM development cycle is composed of several sprints of the same fixed duration. A new sprint begins immediately after the previous one. The amount of sprints in a development cycle is dependent on the complexity of the product.

SCRUM is based on the following agile principles:

1. Iterative and incremental development
?    Iterative: the development is done in short and repetitive cycles (iterations.)Each iteration builds on the results and experience obtained in the previous ones.
?    Incremental: each iteration produces tangible and functional output, providing added value over the results of previous cycles.

2. Multi-purpose and self-organized teams
?    Multi-purpose: though there is some specialization, team members are encouraged to go beyond their usual competences, and assist and learn from their teammates.
?    Self-organized: though each team is led by a coordinator (Scrum Master), teams are expected to become gradually more independent, setting their own priorities, assigning tasks and becoming responsible for their execution. A SCRUM team is considered to be fully mature when they no longer need a Scrum Master.

3. Timeboxing
?    Timeboxing is a time management technique in which work is divided into tasks, and their execution is limited to a short and fixed time duration. This simplifies prioritizing goals, and reduces procrastination and the tendency to extend deadlines.

Now, coming back to the key point of the debate of which is better, SCRUM or PMBOK...

Are SCRUM and PMBOK mutually exclusive?  NO.
PMBOK is a general framework, applicable to any kind of project, and it’s not prescriptive of any specific method. So, let’s say it loud and clear:

PMBOK is NOT a method.

It’s a framework, a set of good practices, a guideline for applying project management techniques and tools, and contains a naming convention… The Project Manager will determine which of the available processes are suitable for the project, and is free to combine them with any method.

SCRUM is a specific methodology, with clearly defined steps, aimed at product development, especially software. It covers product development but does not include key management processes such as acquisitions, human resources, programs and portfolio relationships, etc.

?Are SCRUM and PMBOK complementary? YES.
?    PMBOK provides a global and general view of many aspects of project management and is a useful reference for any environment regardless of the chosen methodology.
?    SCRUM is dynamic approach and promotes a change of work culture, even when it’s not followed purely and only a few of its elements are put into practice.

In conclusion… Is one better than the other? NO.
In general, the best results from each methodology will depend on the specific environment and kind of project. Because of this it is our responsibility as Project Managers (or our organization’s, through its policies) to choose the most appropriate management tools. And a specific methodology such as SCRUM is not fit for direct comparison with a general framework as PMBOK. They are not mutually exclusive, they complement each other.

The effectiveness of any methodology will depend on its fit within the company and its proper implementation.

What do you think?