Scrum Framework

Scrum is the most practiced Agile framework worldwide. According to the 17th Annual State of Agile Report, nearly 70% of Agile teams use Scrum or a hybrid of Scrum. For the PMP exam, understanding Scrum's structure is essential.

Scrum Overview

Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems. The Scrum framework consists of exactly:

• 3 Roles (accountabilities)
• 5 Events (ceremonies)
• 3 Artifacts

Nothing more, nothing less. This simplicity is intentional -- it provides structure while remaining flexible.

---

The Three Scrum Roles

Product Owner

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.

Key Point: The Product Owner is one person, not a committee. They may represent stakeholder desires, but decisions about the Product Backlog belong to the Product Owner alone.

Scrum Master

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They serve the team through servant leadership.

The Scrum Master ensures Scrum is understood and practiced correctly. They are often called a "servant-leader" -- leading by serving others.

Developers

Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint.

Note: "Developers" refers to anyone doing the work, regardless of their specific discipline (coding, testing, design, etc.).

---

The Five Scrum Events

All Scrum events are time-boxed, meaning they have a maximum duration. If work remains, it continues at the next occurrence of the event.

1. The Sprint

The Sprint is a container for all other events. It is a fixed-length iteration (typically 2-4 weeks) during which a "Done," usable, potentially releasable Increment is created.

2. Sprint Planning

Sprint Planning initiates the Sprint by laying out the work to be performed.

Time-box: Maximum 8 hours for a one-month Sprint.

3. Daily Scrum

The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.

• Held at the same time and place every day
• Developers decide how to conduct it
• Focuses on progress and adaptation, not status reporting
• The Scrum Master ensures it happens but Developers run it

4. Sprint Review

The Sprint Review inspects the outcome of the Sprint and determines future adaptations.

Time-box: Maximum 4 hours for a one-month Sprint.

5. Sprint Retrospective

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements.

• What went well?
• What didn't go well?
• What will we improve?

Time-box: Maximum 3 hours for a one-month Sprint.

---

The Three Scrum Artifacts

Each artifact contains a commitment that provides transparency:

Product Backlog

• Single source of work for the Scrum Team
• Constantly evolving (refinement is ongoing)
• Ordered by value, risk, dependencies, and need
• Product Owner is accountable for its content and ordering

Sprint Backlog

• The Sprint Goal (why)
• Product Backlog items selected for the Sprint (what)
• Actionable plan for delivering the Increment (how)
• Owned by Developers

Increment

• A concrete stepping stone toward the Product Goal
• Must be usable and meet the Definition of Done
• Multiple Increments may be created within a Sprint
• Can be delivered to stakeholders at any time

---

The Five Scrum Values

These values enable Scrum's three pillars: Transparency, Inspection, and Adaptation.

---

Scrum at a Glance

Product Backlog --> Sprint Planning --> Sprint Backlog
                         |
                         v
                    Daily Scrum (daily)
                         |
                         v
                    Sprint (1-4 weeks)
                         |
              +----------+-----------+
              |                      |
              v                      v
        Sprint Review      Sprint Retrospective
              |                      |
              v                      v
         Increment               Improvements

---

Key Takeaways

• Scrum has 3 roles, 5 events, and 3 artifacts -- no more, no less
• The Product Owner owns the backlog and maximizes value
• The Scrum Master serves the team through servant leadership
• All events are time-boxed with maximum durations
• The five Scrum values enable transparency, inspection, and adaptation