About Scrum


Scrum is a framework for incremental product development. It uses one or more teams of about seven people. It provides structure of rules, roles, meetings and artefacts. Scrum uses fixed length iterations called Sprints which are typically 1-2 weeks long (never more than 30 days).

It is an alternative to basic Waterfall model which contains six steps as Requirement, Design, Code, Integration, Testing and Deploy. But the main drawback of this method is we are not totally aware of the concepts at the beginning. So when the project development begins we face some serious issues. Using scrum we can avoid this problem. Because in the scrum we concentrate on a single module at a time.

Basic concepts of Scrum:

Product Backlog

In the beginning, product owner will priorities the every task and will be arranged in descending order i.e. highest priority task will be at the top. This is called product backlog.


Tasks in the product backlog will be taken from the top. And assigned to the team. This task is called Sprint.

Sprint Backlog

It has two sections. One is committed backlog items representing “what” and sprint tasks representing “how”.

There are three roles in Scrum:

  • Product Owner
  • Scrum Development Team
  • Scrum Master

Product Owner

Product owner is the person who will finalize product backlog. He makes the final calls of every sprint. He must have vision behind product development. Product owner concentrates on “what” not on “how”.

Scrum Development Team:

It is a cross-functional group responsible to develop potentially shippable product. The team should be self-organizing and all team members must co-operate with each other.

Scrum Master

Scrum master acts as facilitator between product owner and scrum development team. He protects the team from distractions and interruptions. Helps people teach how to use scrum. Promotes improved engineering practices.

How it works

First the product owner will divide the products into smaller parts called “sprints” and add them into product backlog. These sprints will be arranged in the descending order according to their priority. Then the meeting will be arranged and the team will take highest priority sprint and break it into “what” and “how” categories. During the execution of sprint, the team will collaborate with each other every day at least for 15 minutes and everyone will update on their tasks.

At the sprint review meeting, the team will give the update on sprint to product owner. Then owner will decide which part is done and which part is not. If there are some changes to make then product owner or stakeholder will mention so. The team will work on the given updates. This process will go on until the potentially shippable product is developed.

When the sprint is complete the team will select the next sprint from product backlog. And the same process goes on. At the end of each sprint feedback will be given on what went well and what went wrong.

Leave a Reply