Scrum

Last updated Apr 3, 2023

• Sapling
• Project

A lightweight, customer-centric framework. Arguably the most common Agile Approach framework.

• All or nothing framework: you use every part of scrum or it isn’t scrum

• Commitment
• Focus
• Openness
• Respect
• Courage

• Transparency
• Inspections
• Adaptation

• Product owner prioritizes work into a product backlog
• Scrum team selects the top items in the backlog. The top items create a sprint backlog, which will deliver a working product that helps solve the top problem in the product backlog
• Scrum team and Stakeholders review the sprint results and adapt the product and the team’s approach for the next sprint
• The steps repeat as long as the product backlog exists

• Scrum Team
• Product Owner
• Scrum Master
• Developers

• Increment
• Sprint
  • Sprint Planning
    • The Product Owner discusses the highest-priority items in the Product Backlog and how they erlate to the Product Goal. The team creates a Sprint Backlog by breaking down Product Backlog Items (PBIs) into smaller pieces of work. The team is wholly responsible for deciding how to deliver work. Usually lasts eight hours for one-month sprints and less for shorter sprints.
  • Daily Scrum
    • Developers meet to review progress toward the Sprint Goal and plan the next 24 hours of work. Developers should self-organize and sue this time to create plans, review issues, and make decisions. The daily scrum lasts for 15 minutes every working day.
  • Sprint Review
    • The Agile team shares their progress with Stakeholders. Demonstrating small pieces of work reveals valuable information. It uncovers issues early when they are small and easy to fix, reveals previously unknown development ideas, or confirms that the team is on track. Typically, the group shares their progress and the stakeholders provide feedback and ask questions. All attendees discuss where to go next, and the Product Owner may adjust the Product Backlog based on the sprint review. A sprint review lasts four hours for one-month sprints and less for shorter sprints.
  • Sprint Retrospective
    • the team inspects how they worked in the past sprint and identifies improvement opportunities. The retrospective is the only event that isn’t concentrated on the product. Instead, the retrospective focuses on the Scrum Team and how they work together. The event lasts three hours for one-month sprints and less for shorter sprints.

• Strengths
  • Lightweight framework
  • Flexible
  • Responsive learning
  • Complex Problem Solving
  • Less time between planning and the first finished product
  • Good pacing and task breakdown
  • Continuous improvement and adaptation
• Weaknesses
  • Depends on precise circumstances
  • 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, so less experienced teams could struggle
  • Hard to scale to large groups
  • Lost of meetings