Skip to content

13. Scrum

Agile is a project management philosophy that emphasizes iterative development, collaboration, and flexibility. It focuses on delivering working software in short cycles while adapting to changing requirements.

Scrum is the most popular Agile framework that organizes work into time-boxed iterations called Sprints (typically 1-4 weeks). It provides structure through defined roles, events, and artifacts.

The chapter is based on The Scrum Guide.

13.1 Scrum Roles

13.1.1 Product Owner

  • Defines product vision and requirements
  • Manages and prioritizes the Product Backlog
  • Makes decisions about what gets built

13.1.2 Scrum Master

  • Facilitates Scrum events and processes
  • Removes impediments for the team
  • Coaches the team on Agile practices

13.1.3 Development Team

  • Cross-functional team that builds the product
  • Self-organizing and responsible for delivery
  • Typically 3-9 members

13.2 Scrum Events (Meetings)

scrum
What is Scrum?

13.2.1 Sprint Planning

  • Purpose: Plan work for upcoming Sprint
  • Team selects items from Product Backlog and creates Sprint Goal

13.2.2 Daily Scrum (Stand-up)

  • Duration: 15 minutes
  • Purpose: Synchronize team activities
  • Each member shares: What did I do yesterday? What will I do today? Any impediments?

13.2.3 Sprint Review

  • Purpose: Demonstrate completed work to stakeholders
  • Gather feedback and adapt Product Backlog

13.2.4 Sprint Retrospective

  • Purpose
    • Team reflects on process and identifies improvements
    • Builds trust and psychological safety
    • Team takes responsibility for their own improvement process

13.3 Sprint Retrospective - The 5 Phases

The Sprint Retrospective is crucial for continuous improvement. It follows a structured approach with five distinct phases. Use the Retromat to plan your retrospective.

13.3.1 Phase 1: Set the Stage

  • Welcome participants and create psychological safety
  • Establish focus and remind everyone of the retrospective's purpose
  • Set ground rules and expectations
  • Activities: Check-in rounds, weather report, or simple icebreakers

13.3.2 Phase 2: Gather Data

  • Collect information about what happened during the Sprint
  • Create shared understanding of events, feelings, and facts
  • Focus on objective observations rather than interpretations
  • Activities: Timeline creation, mad/sad/glad exercises, or data collection

13.3.3 Phase 3: Generate Insights

  • Analyze the gathered data to identify patterns and root causes
  • Move from "what happened" to "why it happened"
  • Encourage team members to think systemically about issues
  • Activities: 5 Whys analysis, fishbone diagrams, or dot voting on themes

13.3.4 Phase 4: Decide What to Do

  • Prioritize insights and select specific actions for improvement
  • Create concrete, actionable commitments
  • Ensure actions are SMART (Specific, Measurable, Achievable, Relevant, Time-bound)
  • Activities: Action planning, commitment making, or selecting top priorities

13.3.5 Phase 5: Close the Retrospective

  • Summarize decisions and commitments
  • Evaluate the retrospective session itself
  • Thank participants and provide closure
  • Activities: ROTI (Return on Time Invested), appreciation round, or commitment confirmation