Scrum


Scrum is a methodology that focuses on iterative and incremental delivery of products.

  • lightweight, customer-centric framework
  • popular for:
    • simple approach
    • high productivity
    • its scope for applicability to multiple areas
  • delivers iterative and adaptive value while intentionally covering only the barest requirements
  • uses empiricism and lean thinking to improve results continually
    • Empiricism encourages teams to make decisions based on what they see and know
    • Lean thinking drives efficiency by reducing waste, redundancy, and other unnecessary work
  • all-or-nothing framework
    • must use all parts of Scrum, or it isn’t Scrum
  • elements of the framework are highly dependent on each other

Scrum Values

  • describes how people should approach each other:
    1. Commitment
    2. Focus
    3. Openness
    4. Respect
    5. Courage

Scrum Pillars

  • represent how teams should treat the work:
    1. Transparency
      • sharing information improves decisions
    2. Inspection
      • frequent reviews disclose problems and needed changes
    3. Adaption
      • incorporating results of inspection

Scrum Process

  1. The product owner prioritizes work into a product backlog
  2. The Scrum team selects the top items in the backlog and plans the implementation during an event called sprint
    • The top items create a sprint backlog
      • delivers a working product that helps solve the top problem in the product backlog
  3. The scrum team completes the list of objectives while assessing progress in daily meetings called scrums
  4. The Scrum team and stakeholders review the sprint results and adapt the product and the team’s approach for the next sprint
  5. The steps repeat as long as the product backlog exists

Roles

  • Scrum team
    • the group of people who work together to deliver increments of value
    • includes one Scrum leader, one product owner, and developers
    • holds all the capabilities to deliver a product increment each sprint
    • usually >3 but <10 members
  • Product owner
    • A member of a Scrum team who maximizes outcomes and selects and prioritizes the work that the agile team will complete
    • one per team and can serve on multiple agile teams
    • creates, maintains, and owns the product backlog
  • Scrum leader
    • The scrum leader enables the team to apply the scrum framework through coaching, training, and guidance
    • help the team, product owner, and organization improve how they apply Scrum
  • Developers
    • not limited to software developers
    • developer is a shorthand term for a Scrum team member
    • can be any job title or function that helps the Scrum team produce value

Scrum Artifacts and Terms

  • Product backlog
    • ordered list of product changes or enhancements
    • should deliver the product goal
  • Product goal
    • describe the product’s longer-term target
  • Sprint backlog
    • plan for the upcoming sprint
  • Sprint goal
    • describe the single objective that the team plans to meet to advance toward the product goal
  • Increment
    • complete body of work that meets the definition of done and moves toward the product goal
    • sprint can have one or many increments
    • needs a definition of done

Scrum Events

Sprint is a Scrum iteration and the container for all other Scrum events.

  • fixed length
    • 1-4 weeks
  • heartbeat of Scrum
  • sets the rhythm of work
  1. Sprint planning
    • A session where the scrum team selects enough work for the upcoming sprint to build a sprint backlog
    • product owner discusses the highest-priority items in the product backlog and how they relate to the product goal
    • team creates a sprint backlog
    • team is wholly responsible for deciding how to deliver work
    • lasts eight hours for one-month sprints and less for shorter sprints
  2. Daily Scrum
    • A meeting in which the complete team gets together for a quick status update
    • developers meet to review progress toward the sprint goal and plan the next 24 hours of work
    • developers self-organize
    • lasts 15 minutes every working day
  3. Sprint review
    • an informal, end-of-sprint meeting of the agile team and product stakeholders
    • The group reviews the product’s newest functionality in a working session
    • They collaboratively adjust the backlog and decide what to work on next
    • lasts four hours for a one-month sprint and less for shorter sprints
  4. Sprint retrospective
    • A process improvement session where an agile team reflects on the previous sprint and identifies ways that the team can improve how they work together
    • only event that isn’t concentrated on the product
    • focuses on the Scrum team and how they can improve how they work together
    • lasts 3 hours for one-month sprints and less for short sprints

Strengths

  • flexibility means it can be used across any industry
  • short cycles allow for responsive learning and complex problem solving
    • less time between planning and the first finished product
  • highly customer-centric
  • Large and long-lived projects benefit from Scrum’s pacing and task breakdown
  • teams benefit from the limited structure
    • allows for continuous improvement and adaptation

Weaknesses

  • elements depend on very precise circumstances and therefore could falter in less-than-ideal conditions
  • relies on the organization to respect the product owner’s decisions about the backlog and priorities
  • designed for a single, high-performing and cross-functional team
    • means that less-experienced teams may struggle
    • scaling up to larger groups might be difficult
  • teams may become overwhelmed by the meeting schedule
  • pace and might suffer a drop in productivity when team members change

Use Cases

  • Ideal for:
    • Highly cohesive, cross-functional teams focused on continual improvement
    • Larger projects, because the product backlog is consistently refined and broken into tasks
    • Complex products with unpredictable workflows
    • Adaptable projects or products with expected unknown requirements