7.2 Scrum Framework

Project Management Professional PMP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Fundamentals

1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam

2 Chapter 2: People Domain Part 1

2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments

3 Chapter 3: People Domain Part 2

3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence

4 Chapter 4: Process Domain - Planning

4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement

5 Chapter 5: Process Domain - Execution & Control

5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure

6 Chapter 6: Business Environment Domain

6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change

7 Chapter 7: Agile & Hybrid Approaches

7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools

8 Chapter 8: Predictive (Waterfall) Approaches

8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control

Free exam prep PMP Project Management Professional Practice Questions 250 questions Study Guide 57 topics Cheat Sheet 62 facts Flashcards 50 cards

7.2 Scrum Framework

Key Takeaways Explain This Topic AI

Scrum consists of exactly 3 roles (Product Owner, Scrum Master, Developers), 5 events, and 3 artifacts

The Product Owner maximizes value by managing the Product Backlog and representing stakeholder needs

The Scrum Master serves as a servant-leader, ensuring Scrum is understood and removing impediments

Sprint events include Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective within a time-boxed Sprint

The five Scrum values -- Commitment, Courage, Focus, Openness, and Respect -- enable the three pillars of transparency, inspection, and adaptation Last updated: October 2026

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.

Responsibility Description Product Goal Defines and communicates the long-term objective Product Backlog Management Creates, orders, and maintains backlog items Stakeholder Representation Acts as the voice of the customer and stakeholders Value Maximization Makes decisions to optimize product value Backlog Transparency Ensures the backlog is visible and understood 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.

Service To How Scrum Team Coaching, removing impediments, facilitating events Product Owner Finding techniques for effective backlog management Organization Leading Scrum adoption, removing barriers between stakeholders and teams 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.

Accountability Description Sprint Backlog Create and manage the plan for the Sprint Quality Adhere to the Definition of Done Daily Adaptation Adjust plans daily toward the Sprint Goal Peer Accountability Hold each other accountable as professionals 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 event of one month or less during which the Developers create usable Increments that meet the Definition of Done.

Characteristic Description Duration One month or less; consistency recommended Sprint Goal A single objective for the Sprint No changes That would endanger the Sprint Goal Scope clarification May be re-negotiated with Product Owner 2. Sprint Planning Sprint Planning initiates the Sprint by laying out the work to be performed.

Topic Question Answered Why is this Sprint valuable? The Sprint Goal is defined What can be Done? Items selected from Product Backlog How will work get done? Developers decompose items into tasks 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.

Activity Purpose Inspect the Increment Demonstrate what was accomplished Discuss what's next Collaborate on upcoming work Adapt the Product Backlog Refine based on stakeholder feedback The Sprint Review is a working session; the Scrum Guide says the Scrum Team should avoid limiting it to a presentation. 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:

Artifact Commitment Purpose Product Backlog Product Goal Ordered list of everything needed in the product Sprint Backlog Sprint Goal Selected items plus plan to deliver the Increment Increment Definition of Done Sum of all completed items meeting quality standards 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

Value Definition Commitment People personally commit to achieving team goals Courage Team members have courage to do the right thing and face tough problems Focus Everyone focuses on Sprint work and team goals Openness The team agrees to be open about work and challenges Respect Team members respect each other as capable, independent people 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 (one month or less) | +----------+-----------+ | | 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

Maximum Time-Box Duration (Hours) for a One-Month Sprint

Test Your Knowledge

Who is accountable for managing the Product Backlog in Scrum?

Scrum Master

Developers

Product Owner

Stakeholders Check Answer Need a hint? AI

Test Your Knowledge

What is the maximum duration of the Daily Scrum?

30 minutes

15 minutes

1 hour

As long as needed Check Answer Need a hint? AI

Test Your Knowledge

Which Scrum event focuses on the team inspecting itself and creating improvement plans?

Sprint Planning

Sprint Review

Sprint Retrospective

Daily Scrum Check Answer Need a hint? AI

Sections you finish are checked off in the contents.

Up Next 7.3 Kanban & Lean Continue learning

Independent exam preparation notice OpenExamPrep is an independent education provider, not affiliated with or endorsed by the exam sponsors named on this site. Exam and certification names identify what our resources help you study for; they do not imply sponsorship, approval, or review of our materials. Unless a resource expressly identifies authorized public material, our practice questions are independently developed simulations, not actual, recalled, or sponsor-provided exam items. We aim to reflect publicly available exam outlines and topic information in our study resources. Coverage, format, and difficulty may differ from the actual exam, and we cannot guarantee that every detail is accurate or current. Confirm exam requirements, fees, and policies with the official exam sponsor.