Understanding the Scrum Framework

Dec 13, 2024

The Scrum Guide

Introduction

  • Scrum Creators: Ken Schwaber & Jeff Sutherland
  • First Guide Published: 2010
  • Latest Update: November 2020

Purpose

  • Aim: To help people understand and implement Scrum.
  • Content: Definition of Scrum, its rules, and framework.
  • Warning: Altering core design or not following rules reduces effectiveness.

Scrum Definition

  • Framework: Lightweight for generating adaptive solutions to complex problems.
  • Roles:
    1. Product Owner: Manages Product Backlog.
    2. Scrum Team: Delivers Increment of value.
    3. Stakeholders: Inspect and adapt for the next Sprint.
  • Principles: Simplicity and incompleteness to allow adaptation and improvement.

Scrum Theory

  • Foundation: Empiricism (knowledge from experience) and lean thinking (reduce waste).
  • Approach: Iterative, incremental for predictability and risk control.
  • Pillars: Transparency, inspection, adaptation.

Scrum Values

  • Key Values: Commitment, Focus, Openness, Respect, Courage
  • Purpose: Guide behavior and decision-making of Scrum Teams.

Scrum Team Structure

  • Components: Scrum Master, Product Owner, Developers
  • Characteristics: Cross-functional, self-managing, small (10 or fewer members).
  • Accountabilities:
    • Developers: Plan and execute Sprint Backlog, adhere to Definition of Done.
    • Product Owner: Maximizes value, manages Product Backlog.
    • Scrum Master: Ensures effective Scrum adoption.

Scrum Events

  • Sprint: Backbone of Scrum (1 month or less).
  • Types of Events:
    • Sprint Planning: Set up work for the Sprint
    • Daily Scrum: Inspect and adapt towards Sprint Goal
    • Sprint Review: Inspect outcome and adapt future plans
    • Sprint Retrospective: Plan quality and effectiveness improvements

Scrum Artifacts

  • Artifacts: Represent work and value, ensure transparency.
  • Commitments:
    • Product Backlog: Ordered list to improve product, tied to Product Goal.
    • Sprint Backlog: Work plan for the Sprint, aligned with Sprint Goal.
    • Increment: Usable stepping stone towards Product Goal, must meet Definition of Done.

End Note

  • Immutable Framework: Scrum must be implemented in its entirety.
  • Acknowledgements: Contributions from various individuals and organizations.

Licensing

  • Creative Commons: Licensed under Attribution Share-Alike.