Scrum Framework

  • Learn about the Scrum framework, its roles (Product Owner, Scrum Master, Development Team), and ceremonies (Sprint Planning, Daily Standup, Sprint Review, Sprint Retrospective).
  • Understand how Scrum facilitates iterative development, prioritization, and collaboration.

Scrum is an Agile project management framework that enables teams to develop and deliver high-quality products incrementally. It emphasizes collaboration, transparency, and adaptability.

Here, we’ll delve into the Scrum framework, including its roles, ceremonies, and core principles, with examples to illustrate each component.

Roles in Scrum:

1. Product Owner (PO):

Responsibilities: The Product Owner is responsible for defining and prioritizing the product backlog, ensuring that the team works on the most valuable features. They act as the voice of the customer.


Activity Definition

2. Scrum Master (SM):

Responsibilities: The Scrum Master is a servant-leader who helps the team understand and apply Scrum principles. They facilitate Scrum events, remove impediments, and ensure the team follows Scrum practices.

Task Organization

3. Development Team:

Responsibilities: The Development Team is a self-organizing, cross-functional group responsible for delivering product increments. They collaborate to complete the work in each sprint.

Scrum Ceremonies (Events):

1. Sprint Planning:

Purpose: Sprint Planning initiates a new sprint and defines what the team will work on during that sprint. It results in a sprint backlog.


scrum methodology

2. Daily Standup (Daily Scrum):

Purpose: Daily Standup is a short, daily meeting where team members share progress, discuss what they plan to work on, and identify any obstacles.

Estimation and Scheduling

3. Sprint Review:

Purpose: Sprint Review is held at the end of each sprint and involves demonstrating completed work to stakeholders, gathering feedback, and adapting the product backlog.

Closing Processes

4. Sprint Retrospective:

Purpose: Sprint Retrospective is a reflective meeting at the end of each sprint. The team discusses what went well, what didn’t, and identifies improvements for the next sprint.

project delivery

Core Scrum Principles:

  1. Empirical Process Control: Scrum is based on the idea that knowledge emerges over time. Teams make decisions based on observations and feedback rather than rigid plans.

  2. Transparency: Scrum promotes openness and visibility of work, progress, and challenges. Everyone involved has access to the same information.

  3. Adaptation: Scrum teams are encouraged to adapt to changes as they occur, ensuring that the product remains aligned with customer needs and market dynamics.

Devendra Kumar

Project Management Apprentice at Google

Leave a Reply