PMBOK vs SCRUM

ABOUT PMBOK

The Project Management Institute (PMI, 2013) states that "PMBOK guide provides guidelines for managing individual projects and defines project management related concept. It also describes the project management life cycle and its related processes, as well as the project life cycle" (p. 1).

PMI (2013) noted that "the PMBOK Guide also contains the standard for managing most projects most of the time across many types of industries. This standard is unique to the project management field and has interrelationships to other project management disciplines such as program management and portfolio management" (p. 18).

The PMI (2013) clearly states that "the project management standards do not address all details of every topic. This standard is limited to individual projects and the project management processes that are generally recognized as good practice" (p. 18).

The PMI (2013) found that "there are ten separate Knowledge Areas that represents a complete set of concepts, terms, and activities that make up a professional field, project management field, or area of specialization. These Knowledge Areas are: Project Integration Management, Project Scope Management, Project Time Management, Project Quality Management, Project Human Resource Management, Project Communications Management, Project Risk Management, Project Procurement Management and Project Stakeholder Management. Each Knowledge Area contained a separate section in the PMBOK Guide" (p. 60).

ABOUT SCRUM

James (n.d.) states that scrum is part of the Agile movement. Which is a response to the failure of the dominant software development project management paradigms (including waterfall) and borrows many principles from lean manufacturing.

As outlined by James (n.d.) that the Agile Manifesto has a declaration of four values and twelve principles that stand in stark contrast to the traditional Project Manager’s Body Of Knowledge (PMBOK). The Agile Manifesto placed a new emphasis on communication and collaboration, functioning software, team self organization, and the flexibility to adapt to emerging business realities.

According to Takeuchi and Nonaka (1986) they defined scrum as a flexible, holistic product development strategy where a development team works as a unit to reach a common goal as opposed to a traditional, sequential approach.

In “SDLC Scrum Process?” (2015), it is stated that scrum has the following characteristics:

• A short, fixed schedule of cycles with adjustable scope, called sprints, to address rapidly changing development needs.
• A repeating sequence of events, milestones, and meetings.
• A practice of implementing and testing new requirements, called stories, to ensure some work is release-ready after each sprint.
• Commonly used roles such as product owner, scrum master, and team member.

PROJECT ROLES

PMBOK

SCRUM

International Scrum Institute. (n.d.) describe the project team includes:

• Product Owner
• Scrum Master
• Scrum Team

The Project Management Institute (PMI, 2013) noted that the project team includes:

• Project manager
• Project management staff
• Project Staff
• Supporting experts
• User / Customer representatives
• Vendors / Suppliers
• Business Partner

Deemer, Benefield, Larman and Vodde (2012) defines the Scrum Master differs from a project manager. The Scrum Master role excludes any such additional people responsibilities. In fact, there is no role of project manager in Scrum, and practicing Scrum with a project manager included may cause difficulties.

PROJECT LIFE CYCLES

PMBOK

SCRUM

James (n.d.) states that scrum blends all development activities into each iteration, adapting to discovered realities at fixed intervals.

Predictive life cycles are ones in which the project scope, and the time and cost required to deliver that scope, are determined as early in the project life cycle as practically possible (PMI, 2013).

SUMMARY

PMBOK Project Management Methodology

Discipline through strict phase progression.

Simple to implement.

Easy to Manage.

Perfect when you know exactly what it takes to get exactly what you want.

SCRUM Project Management Methodology

Scope is verified by the acceptance of each feature by the customer.

Work breakdown structures become feature breakdown structures.

Test-Driven development and cross-functional teams help bring quality assurance and planning activities forward to the beginning of the project, and continue throughout the project.

Bugs are found and fixed in the iteration; features are then accepted by the customer.

REFERENCES

Deemer, P., Benefield, G., Larman, C., & Vodde, B. (2010). The Scrum Primer. Retrieved from http://www.infoq.com/resource/news/2013/02/scrum-primer-book-download/en/resources/scrumprimer2_optimized.pdf

International Scrum Institute. (n.d.). Scrum Roles - The Scrum Team. Retrieved from http://www.scrum-institute.org/Scrum_Roles_The_Scrum_Team.php

James, M . (n.d.). Scrum Methodology. Retrieved from

http://scrummethodology.com

James, M . (n.d.). Scrum Reference Card. Retrieved from

http://scrumreferencecard.com/scrum-reference-card

Project Management Institute. (2013). A guide to the Project Management Body of Knowledge PMBOK Guide (5th ed.). Newtown Square, PA: Author.

SDLC Scrum Process? (2015). Retrieved from

http://wiki.servicenow.com/index.php?title=SDLC_Scrum_Process

Takeuchi, H., & Nonaka, I. (1986). The New New Product Development Game. Retrieved from https://hbr.org/1986/01/the-new-new-product-development-game