Wednesday, February 21, 2018
Home > Development Methodologies > Agile Methodologies > Agile – Scrum Quick Guide In 5 Minutes

Agile – Scrum Quick Guide In 5 Minutes

Scrum Quick Guide


Ken Schwaber and Jeff Sutherland developed Scrum in early 1990s. Agile Methodology is an umbrella term for several iterative and incremental software development methodologies. Scrum is one of the Agile methodologies. Other Agile Methodologies include Extreme Programming (XP), Crystal, Dynamic Systems Development Method (DSDM), Lean Development, and Feature-Driven Development (FDD).

Definition – Scrum is an iterative and incremental agile software development framework for managing product development.”


End users, executives, team members, etc, give features or requirements to build a product. In Scrum, feature or requirement is written from the perspective of end users.

User Story is the feature or requirement from end users. A typical format of a User Story is – “As a (role/who?)………I need (feature/what?)………so that (benefit/why?……” User Stories should have acceptance criteria, dependencies and risks clearly spelled out.


1. Product Backlog: It is a collection of all the User Stories for a product. It is a wish list.

2. Release Backlog: Team decides which User Stories from the Product Backlog go to a particular release of the product. That decided list of User Stories for the release is Release Backlog.

3. Sprint Backlog: A release has multiple sprints. Team selects User Stories from Release Backlog and puts into different sprints. That decided list of User Stories for the sprint is Sprint Backlog.


1. Product Owner: Helps to make sure right features make into the Product Backlog with right priorities. Represents users and customers of the product.

2. Scrum Master: Helps to make sure project is progressing smoothly. Facilitates release planning, scheduling meetings, removing blockers, and reporting.

3. Development Team: Consists of Developers, Testers, Architects, DBAs, etc. Helps in developing and delivering the product to end users.

4. Others (Part of Development Process But DO NOT Belong to Scrum Team): End Users are those who participate in UAT and use the final product. Customers or Business pay for the product. Executives help on high level decision making.


1. Release Planning: Team identifies the User Stories to be worked in a release. Team estimates each User Story with amount of work needed and prioritizes with the help of Product Owner.

How are User Stories Estimated?

There are different techniques of estimating the User Stories. Estimating using Story Points. Assigning Points to US. Fibonacci format is used. Estimating using Hours. Estimated Work is equal to the sum of total amount of work sized or estimated.

2. Sprint Planning: Team will assign User Stories to each Sprint. Team will add tasks to each User Story.

3. Sprints: Sprints are short duration milestones. Sprints usually are of 2-4 weeks. Goal of sprint completion should be to have a ship ready product with list of user stories decided to be included in the sprint.

4. Daily Scrum / Standup: It is a daily quick meeting of the Scrum Team. It lasts usually for 15 minutes. Scrum Master goes through the progress of each planned User Story for the Sprint and each members provide their statuses on the same.

5. Sprint Demo / Review: A ceremony where the work done in the sprint is showcased to all the stakeholders.

6. Sprint Retrospective: A look back at the sprint. Team talks about “what went right” and “what went wrong.” This helps on improving as a team and create more synergy for future sprints.


Burndown Chart: It provides a day by day measure of the amount of work remaining. Work Remaining (Hours) should be in Vertical Grid. Time (Days) should be in Horizontal Grid. The slope of the graph is called Burndown Velocity. This is the average rate of productivity of each day for the team.

Picture Source:

Definition of Done: It varies from teams to teams to define the meaning of “Done” of a User Story. Usually each Scrum Team should come to an agreement to decide when the User Story is supposed to be “Done.” The basic fundamental is that a User Story is Done when all the stakeholders approve the feature based upon the acceptance criteria mentioned.


1. CA Agile Central (Rally)

2. Jira Software



Leave a Reply

Your email address will not be published. Required fields are marked *