You are on page 1of 13

What is Scrum Process?

Where is it used?
How is it better?

Scrum is an iterative incremental process of software development commonly used with agile software development Agile software development focuses on keeping code simple, testing often, and delivering functional bits of the application as soon as they're ready. The goal of ASD is to build upon small client-approved parts as the project progresses, as opposed to delivering one large application at the end of the project.

Scrum in 100 words Scrum is an agile process that allows us to focus

on delivering the highest business value in the shortest time. It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). The business sets the priorities. Teams selforganize to determine the best way to deliver the highest priority features. Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

Everyone answers the following three questions What did you accomplish since last scrum? What will you do before the next scrum? Any blocks? Update the Sprint Burn-down Chart

Holds the vision for the product

Defines the features of the product Prioritizes features according to business value

Maintains a prioritized backlog for the product

Decides on release date and content Is responsible for the ROI of the project
Can change features and priority every sprint Accepts or rejects work results

Ensures that the process is followed Ensures that the team is fully functional and productive
Removes impediments Shields the team from external interferences

Enables close cooperation across all roles, teams, and organizations


Hosts the daily scrum, iteration review and planning meetings
Is not the focal point of these meetings however!

Cross-functional, 7 +/- 2 members Has the right to do everything within the boundaries of the project guidelines to reach the Sprint objectives Organizes itself and its work Provides estimates for releases and sprints
Updates sprint estimates on a daily basis

Commits to the Sprint goal and specifies work results Demos work results to the Product Owner

The sprint backlog consists of a story and description Break each story into small tasks.

Whats the definition of Done?

Product Life varies Release Length variable (at least 3, more is better) Sprint Length repeated fixed duration of 2 4 weeks

Day typically an 8-hour workday

You might also like