SCRUM

Refreshing my knowledge about SCRUM in preparation for the interviews.

The Scrum master serves to facilitate scrum to the larger team by ensuring the scrum framework is followed.

A Scrum Team is a small (typically 10 or fewer) team of people that work together, using the Scrum Framework, to create something valuable. The team consists of:

• A Product Owner who maximizes the value of the product that results from the work of the Scrum Team
• Developers who create the product
• A Scrum Master who helps the team improve its practices and effectiveness

  %%{init: {'theme':'dark'}}%%
  stateDiagram

    sp: Sprint Planning
    ds: Daily Scrum
    sr: Sprint Review
    sretro: Sprint Retrospective
    [*] --> sp
    sp --> ds: Sprint Backlog is prepared during the planning
    ds --> ds: Daily Event timeboxed for 15 minutes
    ds --> sr: End Of Sprint
    sr --> sretro
    sretro --> [*]

Scrum, known for its empirical process framework, revolves around three core pillars:

• transparency
• inspection
• adaptation

  kanban
  Foundation
    empiricism
    lean thinking
    small team of people
  SCRUM pillars
    transparency
    inspection
    adaptation
  Events
    Sprint <= 1 month
    Sprint Planning <= 8h
    Daily Scrum <= 15 mins
    Sprint Review <= 4h
    Sprint Retrospective <= 3h
  Values
    Commitment
    Focus
    Openness
    Respect
    Courage
  Scrum Team
    Scrum Master
    Product Owner
    Developers
  Artifacts & commitment
    Product Backlog -> Product Goal
    Sprint Backlog -> Sprint Goal
    Increment -> Definition of Done

The Scrum Master helps the Scrum Team:

• By coaching the team members in self-management and cross-functionality
• Focus on creating high-value Increments that meet the Definition of Done
• Influence the removal of impediments to the Scrum Team’s progress
• Ensure that all Scrum events take place and are positive, productive, and kept within the timebox.

helps the Product Owner:

• Find techniques for effective Product Goal definition and Product Backlog management
• Provide ways for the Scrum Team to understand the need for clear and concise Product Backlog items
• Establish empirical product planning for a complex environment
• Facilitate stakeholder collaboration as requested or needed

supports the Organization:

• By Leading, training and coaching them in their Scrum adoption
• By helping employees and stakeholders understand and instill an empirical approach for complex work
• Remove barriers between stakeholders and Scrum Teams

What should we remember during the Sprint:

• No changes to endanger Sprint Goal
• Quality does not decrease
• Product Backlog is refined as needed
• Scope can be negotiated & refined with Product Owner as more is learned
• Product Backlog Refinement is handled by Scrum team and does not have specific time box.
• Not completed items are not included into the Product Increment.
• SCRUM teams even on the same Product may have different start/end for the Sprints.
• Only Product Owner can cancel the Sprint, but decision can be based on the input from stakeholders, Scrum master and/ord Developers.

The Scrum framework is immutable. While implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices.

see SCRUM guide for more details.

2025-05-12