What is Scrum?

Scrum is a framework for managing product development using short iterations called Sprints.

Key idea:

  • Work is divided into small tasks
  • Delivered in short cycles (usually 2–4 weeks)
  • Feedback is collected after every sprint

This allows teams to adapt quickly to changes.


Main Components of Scrum

Scrum has three main roles, five events, and three artifacts.


1️⃣ Scrum Roles

1. Product Owner

The Product Owner represents the customer and manages the product requirements.

Responsibilities:

  • Defines product features
  • Prioritizes tasks
  • Maintains the Product Backlog

Example:
If customers request a new feature, the Product Owner adds it to the backlog.


2. Scrum Master

The Scrum Master ensures the team follows Scrum practices.

Responsibilities:

  • Facilitates meetings
  • Removes obstacles
  • Helps the team stay productive

The Scrum Master is not a manager but a facilitator.


3. Development Team

The development team builds the product.

Members may include:

  • Software developers
  • QA engineers
  • UI designers
  • DevOps engineers

Typical team size:

5–9 people

The team is self-organizing.


2️⃣ Scrum Events

Scrum uses five events (meetings).


1. Sprint

A Sprint is a fixed development cycle.

Typical duration:

2 weeks

During the sprint:

  • The team develops features
  • No major changes are allowed

Output:
Working product increment.


2. Sprint Planning

At the start of each sprint.

The team decides:

  • What work will be done
  • How it will be completed

Input:
Product Backlog.

Output:
Sprint Backlog.


3. Daily Standup (Daily Scrum)

A 15-minute daily meeting.

Each team member answers three questions:

  1. What did I do yesterday?
  2. What will I do today?
  3. Are there any blockers?

Purpose:

  • Keep everyone aligned.

4. Sprint Review

At the end of the sprint.

The team:

  • Demonstrates completed features
  • Gets feedback from stakeholders

Example:
Showing a newly implemented login feature.


5. Sprint Retrospective

The team reviews how the sprint went.

Discussion topics:

  • What worked well
  • What didn’t work
  • What can improve

Goal:
Continuous improvement.


3️⃣ Scrum Artifacts

Artifacts are the documents or work items used in Scrum.


Product Backlog

A list of all product requirements.

Examples:

  • User login
  • Payment system
  • Dashboard UI

The Product Owner manages this list.


Sprint Backlog

A subset of tasks selected from the Product Backlog for the current sprint.

Example:

Sprint Backlog
--------------
Implement login API
Create login UI
Write authentication tests

Product Increment

The working software produced at the end of a sprint.

Example:
After Sprint 1 → Login feature completed.


Scrum Workflow Example

Typical Scrum development cycle:

Product Backlog

Sprint Planning

Sprint (2 weeks development)

Daily Standups

Sprint Review

Sprint Retrospective

Next Sprint

Advantages of Scrum

✔ Faster delivery
✔ Better collaboration
✔ Flexible to requirement changes
✔ Continuous improvement
✔ Higher product quality


Scrum vs Traditional Development

ScrumTraditional
Iterative developmentSequential development
Short cyclesLong release cycles
Continuous feedbackLate feedback
Flexible planningFixed planning

Example in Real Projects

Example sprint tasks in a software team:

Sprint 1:

  • Login system
  • Database schema

Sprint 2:

  • User profile
  • Password reset

Sprint 3:

  • Notification system
  • Email verification

Each sprint produces working software.


Summary

Scrum is an Agile framework that helps teams:

  • Work in short development cycles
  • Deliver working software quickly
  • Adapt to changing requirements
  • Improve through continuous feedback