๐ŸŽฏ Ultimate PSPO Study Guide

Master the 2020 Scrum Guide for Product Owner Success

๐Ÿš€ Scrum Framework Overview

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

The Scrum Framework in Action

๐Ÿƒโ€โ™‚๏ธ Sprint (โ‰ค 1 Month)

Sprint Goal: Single objective for the Sprint

๐Ÿ“‹ Sprint Planning

What can be Done? How will it get done?

โ‰ค 8 hours
๐Ÿ—ฃ๏ธ Daily Scrum

Inspect progress, adapt Sprint Backlog

15 minutes
๐Ÿ‘€ Sprint Review

Inspect outcome, determine adaptations

โ‰ค 4 hours
๐Ÿ”„ Sprint Retrospective

Plan ways to increase quality & effectiveness

โ‰ค 3 hours

๐ŸŽฏ Core Scrum Process (The 4-Step Loop)

  1. Product Owner orders work into Product Backlog
  2. Scrum Team turns selection into Increment during Sprint
  3. Team & stakeholders inspect results and adapt
  4. Repeat - continuous improvement cycle

๐Ÿง  Scrum Theory & Pillars

Foundation: Empiricism + Lean Thinking

Empiricism: Knowledge comes from experience and making decisions based on what is observed

Lean Thinking: Reduces waste and focuses on the essentials

๐Ÿ‘๏ธ

Transparency

Process and work visible to performers and receivers

๐Ÿ”

Inspection

Frequent and diligent inspection of artifacts and progress

โšก

Adaptation

Adjust process or materials when outside acceptable limits

๐Ÿ’Ž Scrum Values

Successful use of Scrum depends on people becoming more proficient in living five values

๐Ÿ’ช

Commitment

To achieving goals and supporting each other

๐ŸŽฏ

Focus

Primary focus on Sprint work

๐Ÿ”“

Openness

About work and challenges

๐Ÿค

Respect

Each other as capable, independent people

๐Ÿฆ

Courage

To do the right thing, work on tough problems

๐ŸŒŸ Values in Action

These values give direction to the Scrum Team regarding their work, actions, and behavior. When embodied by the Scrum Team and stakeholders, the empirical Scrum pillars come to life building trust.

๐Ÿ‘ฅ Scrum Team

๐Ÿ›๏ธ Team Structure

  • Small team - typically โ‰ค10 people
  • Cross-functional - all skills to create value each Sprint
  • Self-managing - internally decide who, what, when, how
  • No sub-teams or hierarchies
  • Focused on one objective - the Product Goal

๐ŸŽฏ Product Owner

Accountable for maximizing product value

๐Ÿ›ก๏ธ Scrum Master

Accountable for establishing Scrum & team effectiveness

โš™๏ธ Developers

Committed to creating usable Increment each Sprint

๐Ÿ“… Scrum Events

๐ŸŽฏ Purpose of Events

Each event is a formal opportunity to inspect and adapt Scrum artifacts. Events create regularity and minimize need for undefined meetings.

๐Ÿƒโ€โ™‚๏ธ The Sprint (Container Event)

Heartbeat of Scrum - where ideas are turned into value

  • Fixed length: โ‰ค 1 month
  • New Sprint starts immediately after previous concludes
  • Contains all other events
  • Only Product Owner can cancel Sprint

๐Ÿ“‹ Sprint Planning

Purpose: Lay out work for Sprint

โ‰ค 8 hours (1 month Sprint)
Three Topics:
  1. Why is Sprint valuable? โ†’ Sprint Goal
  2. What can be Done? โ†’ Select from Product Backlog
  3. How will work get done? โ†’ Plan delivery

๐Ÿ—ฃ๏ธ Daily Scrum

Purpose: Inspect progress toward Sprint Goal

15 minutes
  • For Developers of Scrum Team
  • Same time & place every working day
  • Focus on progress toward Sprint Goal
  • Produces actionable plan for next day

๐Ÿ‘€ Sprint Review

Purpose: Inspect Sprint outcome, determine adaptations

โ‰ค 4 hours (1 month Sprint)
  • Present results to stakeholders
  • Discuss progress toward Product Goal
  • Collaborate on what to do next
  • Working session, not just presentation

๐Ÿ”„ Sprint Retrospective

Purpose: Plan ways to increase quality & effectiveness

โ‰ค 3 hours (1 month Sprint)
  • Inspect how last Sprint went
  • Identify most helpful changes
  • Address most impactful improvements
  • Concludes the Sprint

๐Ÿ“‹ Scrum Artifacts

๐ŸŽฏ Purpose of Artifacts

Artifacts represent work or value and are designed to maximize transparency of key information. Each artifact has a commitment to enhance transparency and focus.

๐Ÿ“‹ Product Backlog

Emergent, ordered list of what's needed to improve the product

Commitment: Product Goal

๐Ÿ“ Sprint Backlog

Sprint Goal + selected Product Backlog items + plan for delivery

Commitment: Sprint Goal

โœ… Increment

Concrete stepping stone toward Product Goal

Commitment: Definition of Done

๐ŸŽฏ Product Owner Deep Dive

๐Ÿ† Core Accountability

Maximizing the value of the product resulting from the work of the Scrum Team

๐ŸŽฏ Product Goal Mastery

The Product Goal is the long-term objective for the Scrum Team. It describes a future state of the product and serves as a target for planning.

  • Team must fulfill or abandon one objective before taking next
  • Lives in the Product Backlog
  • Rest of Product Backlog emerges to define "what" will fulfill it

๐Ÿ“‹ Product Backlog Management Excellence

๐Ÿค Stakeholder Collaboration

Product Owner represents needs of many stakeholders in Product Backlog. Those wanting changes must convince the Product Owner.

  • One person, not a committee
  • Organization must respect PO decisions
  • Decisions visible in Product Backlog content and ordering
  • Results visible in Sprint Review Increments

๐Ÿ”„ PO in Sprint Events

Sprint Planning

  • Ensure attendees prepared to discuss important items
  • Explain how product could increase value
  • Collaborate to define Sprint Goal
  • Help Developers select items from Product Backlog

Daily Scrum

  • Participate as Developer if working on Sprint Backlog items
  • Otherwise, not required to attend

Sprint Review

  • Present results to stakeholders
  • Discuss progress toward Product Goal
  • Collaborate on what to do next
  • May adjust Product Backlog based on feedback

Sprint Retrospective

  • Participate as Scrum Team member
  • Focus on improving effectiveness

๐Ÿงช PSPO Practice Quiz

Test your knowledge with these official Scrum Guide based questions

Question 1: Product Owner Accountability

What is the Product Owner accountable for?

  • Managing the Development Team
  • Maximizing the value of the product resulting from the work of the Scrum Team
  • Writing all Product Backlog items personally
  • Attending all Daily Scrums
Correct! The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They may delegate work but remain accountable.

Question 2: Product Goal

Where does the Product Goal live?

  • In the Product Backlog
  • In the Sprint Backlog
  • In a separate document
  • In the Definition of Done
Correct! The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define "what" will fulfill the Product Goal.

Question 3: Sprint Length

What is the maximum length of a Sprint?

  • 2 weeks
  • 1 month
  • 6 weeks
  • 3 months
Correct! Sprints are fixed length events of one month or less to create consistency. Shorter Sprints can generate more learning cycles.

Question 4: Scrum Values

Which of the following is NOT one of the five Scrum Values?

  • Commitment
  • Focus
  • Innovation
  • Courage
Correct! The five Scrum Values are: Commitment, Focus, Openness, Respect, and Courage. Innovation is not one of them.

Question 5: Definition of Done

What happens when a Product Backlog item meets the Definition of Done?

  • It goes to Sprint Review
  • An Increment is born
  • It must be released immediately
  • It returns to Product Backlog
Correct! The moment a Product Backlog item meets the Definition of Done, an Increment is born. The Increment may be delivered before Sprint end.

Question 6: Daily Scrum

Who is the Daily Scrum for?

  • The entire Scrum Team
  • The Developers of the Scrum Team
  • The Product Owner only
  • All stakeholders
Correct! The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. PO and SM participate as Developers if actively working on Sprint Backlog items.

Question 7: Sprint Cancellation

Who has the authority to cancel a Sprint?

  • Scrum Master
  • Product Owner
  • Developers
  • Stakeholders
Correct! Only the Product Owner has the authority to cancel the Sprint, typically when the Sprint Goal becomes obsolete.

Question 8: Scrum Team Size

What is the recommended size for a Scrum Team?

  • 5-7 people
  • 10 or fewer people
  • 3-5 people
  • 15 people maximum
Correct! Scrum Teams are typically 10 or fewer people. Smaller teams communicate better and are more productive.