Scrum Guide for PMP Exam Preparation

Purpose of Scrum

Scrum is a framework designed to solve complex problems while delivering maximum value. Developed by Ken Schwaber and Jeff Sutherland, it promotes iterative, incremental progress through a team-focused approach. The Scrum Guide for PMP Exam outlines the essential roles, events, artifacts, and rules required to implement Scrum effectively. This guide helps teams solve problems adaptively in dynamic environments, aiming to uncover issues early, adapt continuously, and enhance collaborative productivity.

Scrum Theory

Scrum is based on empiricism and lean thinking:

1. Empiricism – Decisions are based on experience and observation.
2. Lean Thinking – Reduces waste and focuses on what is essential.

Scrum employs an iterative, incremental approach to control risk and increase predictability.

Scrum Values

Success with Scrum depends on embodying its core values:

1. Commitment – Team members are committed to achieving the goals.
2. Focus – Priority is given to the current Sprint’s work.
3. Openness – Challenges and issues are openly discussed.
4. Respect – Team members are seen as capable and are respected as such.
5. Courage – Team members have the courage to tackle challenging problems.

These values foster trust and transparency, which are critical for effective inspection and adaptation, the two pillars of Scrum empiricism.

Scrum Framework Overview

1. Scrum Roles

There are three key roles within Scrum that make up the Scrum Team:

a. Product Owner

• Accountable for maximizing the product’s value.
• Manages the Product Backlog, ensuring items are ordered based on priority.
• Works closely with stakeholders to communicate the product vision.

b. Scrum Master

• Facilitates Scrum, ensures adherence to the Scrum framework.
• Coaches the team on self-management and cross-functionality.
• Helps the Product Owner with backlog management and stakeholder collaboration.
• Ensures Scrum events are conducted effectively.

c. Developers

• Responsible for creating each Sprint’s Increment.
• Accountable for planning the Sprint Backlog and maintaining quality through adherence to the Definition of Done.
• Work collaboratively to meet the Sprint Goal and adapt their plan as necessary during the Sprint.

The Scrum Team is self-managing, cross-functional, and works as a unit to accomplish the Product Goal.

2. Scrum Events

Scrum employs five formal events, each structured to foster adaptation and transparency:

a. Sprint

• A timeboxed period (typically 1–4 weeks) where the team focuses on delivering an Increment.
• During the Sprint, no changes are made that could endanger the Sprint Goal.
• Contains all other Scrum events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

b. Sprint Planning

• Timeboxed to 8 hours for a one-month Sprint (proportionally shorter for shorter Sprints).
• The Scrum Team defines the Sprint Goal and selects items from the Product Backlog.
• Planning focuses on why the Sprint is valuable, what can be done, and how to accomplish it.

c. Daily Scrum

• A 15-minute daily meeting focused on the Sprint Goal.
• Developers discuss progress, identify obstacles, and adjust the plan for the day.
• Enhances transparency, communication, and self-management within the team.

d. Sprint Review

• Timeboxed to 4 hours for a one-month Sprint.
• The team demonstrates the Increment and collects feedback from stakeholders.
• Adjustments to the Product Backlog are made based on this feedback to drive further adaptations.

e. Sprint Retrospective

• Concludes each Sprint; timeboxed to 3 hours for a one-month Sprint.
• The team reflects on processes, relationships, and tools to identify improvement opportunities.
• Aims to enhance quality and efficiency in the next Sprint.

3. Scrum Artifacts

Scrum defines three key artifacts to bring transparency and ensure alignment on work progress and goals:

a. Product Backlog

• The dynamic list of items, features, or changes to achieve the Product Goal.
• Continuously refined by the Product Owner; items at the top are typically prioritized and more detailed.

b. Sprint Backlog

• Contains the Sprint Goal, selected Product Backlog items, and a plan to achieve them.
• Owned and updated by Developers; provides a real-time picture of current Sprint work.

c. Increment

• A step toward the Product Goal, meeting the Definition of Done and deliverable.
• All completed items from the Sprint Backlog constitute the Increment.

Each artifact has a commitment:

• Product Goal for the Product Backlog.
• Sprint Goal for the Sprint Backlog.
• Definition of Done for the Increment.

Key Scrum Commitments

1. Product Goal – The future state of the product; provides a long-term objective.
2. Sprint Goal – A short-term goal for each Sprint, providing direction and focus.
3. Definition of Done – A shared understanding of the Increment’s completion criteria.

Application of Scrum for PMP Exam Success

Understanding Scrum’s empirical processes, self-managing teams, and iterative value delivery is essential for project managers, especially in complex or high-uncertainty projects. Scrum practices align with the PMBOK’s Agile approach for projects that require adaptability, quick feedback loops, and close collaboration with stakeholders.

Preparing for PMP Exam can be super easy with 800+ PMP Terms - Buy Now