DevOps
  • Introduction
    • About DevOps
    • Software Production
    • Software System
  • Terminal Programming
    • BASH - Basics Commands
    • BASH -Conditions and Loops
    • Some Examples
  • SOFTWARE TEAMS
    • Software Teams
      • Software Team Topologies
      • Effort-Cost Estimation
      • Technical Debt
      • Software Development Waste
    • Software Production Methods
      • SCRUM
      • KANBAN
      • WATER FALL
      • AGILE
    • Version Control
    • CAMS
  • CI/CD
    • Continuous Integration & Continuous Delivery
  • Cloud Platforms
  • Automation Strategies
  • PaaS - Containers
    • Docker
  • PaaS - Orchestration
    • Kubernetes
  • DevOps & DORA Metrics
  • Monitoring Tools
  • A Day in a DevOps
  • MLOps
Powered by GitBook
On this page
  • Core Components
  • Scrum Accountabilities
  • Scrum Artifacts
  • Scrum Events
  • The Three Pillars of Scrum
  • The Five Scrum Values
  • Six Scrum Principles
  • Key Concepts
  1. SOFTWARE TEAMS
  2. Software Production Methods

SCRUM

https://www.scrum.org/ - Office website for understanding SCRUM Processes

PreviousSoftware Production MethodsNextKANBAN

Last updated 3 months ago

Scrum is a lightweight framework designed to help teams collaborate on complex products iteratively and incrementally to deliver high value. It is built on the principles of empiricism and lean thinking. Here's a comprehensive overview of Scrum:

Core Components

Scrum consists of three main components:

  1. Accountabilities (formerly called roles)

  2. Artifacts

  3. Events

Scrum Accountabilities

  1. Developers: Professionals who create any aspect of the product increment during sprints

  2. Product Owner: Develops and communicates the product goal, owns the product backlog, and ensures the team addresses high-value work

  3. Scrum Master: Guides the organization in Scrum adoption and practice, coaches the team, and helps manage impediments

Scrum Artifacts

  1. Product Backlog: A prioritized list of features and requirements for the product.

  2. Sprint Backlog: A subset of the product backlog items selected for a specific sprint.

  3. Increment: The potentially shippable product at the end of each sprint.

Scrum Events

  1. Sprint: A time-boxed period (usually 2-4 weeks) during which a potentially releasable product increment is created

  2. Sprint Planning: A meeting to plan the work for the upcoming sprint.

  3. Daily Scrum: A brief daily meeting for the team to synchronize activities and create a plan for the next 24 hours.

  4. Sprint Review: A meeting at the end of the sprint to inspect the increment and adapt the product backlog.

  5. Sprint Retrospective: A meeting for the team to reflect on their process and plan improvements.

The Three Pillars of Scrum

Scrum is based on empirical process control, which relies on three fundamental pillars

  1. Transparency: Ensuring all aspects of the work are visible to those responsible for the outcomes

  2. Inspection: Regularly examining Scrum artifacts and progress toward the Sprint Goal

  3. Adaptation: Adjusting the process or product when deviations are detected

The Five Scrum Values

  1. Commitment: Dedicating oneself to the team's goals and quality standards

  2. Courage: Having the bravery to face challenges and make tough decisions

  3. Focus: Concentrating on the most crucial goals and tasks

  4. Openness: Being transparent about work and challenges

  5. Respect: Valuing team members' opinions and skills

Six Scrum Principles

  1. Empirical Process Control: Basing decisions on observation, experience, and experimentation

  2. Self-organization: Empowering teams to work independently and make decisions

  3. Collaboration: Promoting awareness, articulation, and appropriation among team members

  4. Value-based Prioritization: Organizing and prioritizing tasks based on their value

  5. Time-boxing: Allocating specific time frames for activities to manage planning and execution effectively

  6. Iterative Development: Continuously improving and adapting the product through repeated cycles

Key Concepts

  1. Iterative and Incremental: Scrum combines both approaches, allowing for repeated cycles of improvement and delivering functionality in small batches

  2. Self-managing Teams: Scrum teams are cross-functional and self-organizing, with the flexibility to adapt to changing requirements

  3. Continuous Improvement: Through regular inspection and adaptation, Scrum teams strive for ongoing enhancement of their processes and products

Scrum's effectiveness lies in its simplicity and flexibility, making it suitable for various industries and project types. By adhering to these principles, values, and practices, teams can effectively manage complex work, adapt to changes, and deliver high-value products to their customers.

3
Overall Scrum Process Across the Software Product Development. Credits:
https://www.pm-partners.com.au/