Scrum

Scrum is one of the most popular agile methodologies that focuses on iterative and incremental development of products (e.g. software).Scrum delivers products in short timeboxed-iterations. Each iteration starts after a planning game and ends with a demo and retrospective.

Related methods and techniques to Scrum

  • Scrum Timeboxing

    1. Scrum Timeboxing

    Some example of Scrum timeboxes that are observed in Scrum Agile teams include:

    Iterations and sprints – 1 to 4 weeks
    Sprint Planning – 2-8 Hours
    Daily standup meetings – 15 minutes
    Sprint review – 1-4 Hours
    Retrospective – 45 min.-3 hours

  • Pillars of Scrum

    2. Pillars of Scrum

    The Scrum methodology is based on three pillars:

    1. Transparency
    2. Inspection
    3. Adaptation
  • Scrum Roles

    3. Scrum Roles

    In Scrum there are three main roles, namely:

    • Product Owner
    • Scrum Master
    • Development Team
  • Scrum Ceremonies

    4. Scrum Ceremonies

    Scrum has four meetings that all members of the Scrum team would attend.

    • Sprint Planning
    • Daily Scrum Meeting
    • Sprint Review
    • Sprint Retrospective
  • Scrum Artifacts

    5. Scrum Artifacts

    Within the Scrum team, there are a number of deliverables that are provided by different roles.

    • Product Backlog: Product Backlog is a list of requirements that are typically managed by the product owner and ordered sequentially based on factors such as business value, risk, dependencies, and required delivery dates.
    • Sprint backlog: In sprint planning meetings, the items in the Product Backlog are prioritized according to their estimated size or complexity and divided into time-bound sprints. this list is referred to as the "Sprint Backlog".
    • Definition of done: the team should agree on how items in the backlog will be marked as complete.
    • Product Increment: each iteration creates a product increment that is integrated into or builds upon an existing product. It must meet the acceptance criteria set by the product owner, meet the team's definition of "done," and be of sufficiently high quality to be delivered to users.
    • Burndown charts: the Burndown Charts shows the team's progress toward the defined goal, expressed in terms of the number of story points remaining in the current sprint.
  • Scaling Scrum

    6. Scaling Scrum

    The optimal size of a Scrum team is 7±2 members. However, for large and complex projects, the team needs to be scalable.
    Scrum-of-Scrums is a scalability approach that enables scalability through a team of teams. It follows the same format as the daily stand-up. However, resolving the dependencies between delivery teams becomes very complex and is a big challenge. Scaling Micro Agile (SMART) is a Swiss-made scalability approach that addresses these challenges. SMART solves the multi-team agile planning problem, automatically organizes dependencies, and eliminates late and lengthy large-room agile plans.