SCRUM

Presented By:

100553X Uruththirakodeeswaran.T

100234V Kamalabalan.K

100152R Gitanjali . T

SCRUM IN 100 WORDS

Scrum is an agile process that allows us to focus on delivering thehighest business value in the shortest time.

Scrum is based on three simple principles: visible progress, constantinspection, and adaptation

Every two weeks to a month anyone can see real working softwareand decide to release it as is or continue to enhance it for anothersprint.

It allows us to rapidly and repeatedly inspect actual workingsoftware (every two weeks to one month).

The business sets the priorities. Teams self-organize to determinethe best way to deliver the highest priority features.

HISTORY OF SCRUM

1995: - Analysis of common software development processes not

suitable for empirical, unpredictable and non-repeatable processes

- Design of a new method: Scrum by Jeff Sutherland & Ken Schwaber

- Enhancement of Scrum by Mike Beedle & combination of Scrum with Extreme Programming

1996:- introduction of Scrum at OOPSLA conference

2001:- publication “Agile Software Development with Scrum” by Ken

Schwaber & Mike Beedle

Successful appliance of Scrum in over 50 companiesFounders are members in the Agile Alliance

SCRUM HAS BEEN USED BY

Microsoft Yahoo Google Electronic Arts High Moon Studios Lockheed Martin Philips Siemens Nokia Capital One BBC Intuit

Intuit Nielsen Media First American Real Estate BMC Software Ipswitch John Deere Lexis Nexis Sabre Salesforce.com Time Warner Turner Broadcasting Oce

SCRUM HAS BEEN USED FOR

Commercial software In-house development Contract development Fixed-price projects Financial applications ISO 9001-certified

applications Embedded systems 24x7 systems with

99.999% uptime requirements

the Joint Strike Fighter

Video game development FDA-approved, life-critical

systems Satellite-control software Websites Handheld software Mobile phones Network switching

applications ISV applications Some of the largest

applications in use

SCRUM FRAMEWORK AT GLANCE

COMPONENTS OF SCRUM

Scrum roles

The process

Scrum artifacts

Product owner

Representative from the business side

Decide on release date and content

Be responsible for the profitability of the product (ROI)

Prioritize features according to market value

Must be highly available throughout the project development time

Accept or reject work results

Scrum master

Acts as facilitator for product owner and team

Responsible for enacting Scrum values and practices and removing impediments

Ensure that the team is fully functional and productive

Enable close cooperation across all roles and functions

Shield the team from external interferences

The Team

Typically 5-9 people

Cross-functional:

- Developers, Testers, Business Analysts, Specialist like UI Designers, etc.

The development team provides estimates and does the work.

Members should be full-time

- May be exceptions (e.g., database administrator)

The Team

Team collaboration and self-organization are key practices in Scrum teams

Membership should change only between sprints

SPRINTS

Scrum projects make progress in a series of “sprints”- A Sprint is an iteration in which the team works on the

Sprint Backlog- Analogous to Extreme Programming iterations

Typical duration is 2–4 weeks or a calendar month at most

A constant duration leads to a better rhythm Product is designed, coded, and tested during the

sprint No outside influence can interference with the Scrum

team during the Sprint Each Sprint begins with the Daily Scrum Meeting

NO CHANGES DURING SPRINTS

• Change

Plan sprint durations around how long you

can commit to keeping change out of the

sprint

PRODUCT BACKLOG

The requirements

A list of all desired work on the project

Prioritized by the product owner

Reprioritized at the start of each sprintThis is the

product backlog

Sprint Planning

• Team selects items from the product backlog they can commit to completing

• Sprint backlog is created

– Tasks are identified and each is estimated (1-16 hours)

– Collaboratively, not done alone by the ScrumMaster

• High-level design is considered

PRE-PROJECT/KICKOFF MEETING

A special form of Sprint Planning Meeting

Meeting before the begin of the Project

SPRINT BACKLOG

A subset of Product Backlog Items, which define the work for a Sprint

Is created ONLY by Team members

Each Item has it’s own status

Should be updated every day

DAILY SCRUM

Parameters- Daily

- 15-minutes

- Stand-up

- Not for problem solving

Three questions:1. What did you do yesterday

2. What will you do today?

3. What obstacles are in your way?

SCRUM FAQs

Can Scrum meetings be replaced by emailed status reports?– No

Entire team sees the whole picture every day

Create peer pressure to do what you say you’ll do

SPRINT REVIEW MEETING

Team presents what it accomplished during the sprint

Typically takes the form of a demo of new features or underlying architecture

Inspect and Adapt Activity for the product Informal

- 2-hour prep time rule

Participants- Customers- Management- Product Owner- Other engineers

SPRINT RETROSPECTIVE

Periodically take a look at what is and is not working

Typically 15–30 minutes

Done after every sprint

Whole team participates- Scrum Master- Product owner- Team- Possibly customers and others

START / STOP / CONTINUE

Whole team gathers and discusses what they’d like to:

Start doing

Stop doing

Continue doing

This is just one of many ways to do a sprint retrospective.

SPRINT BURN DOWN CHART

Depicts the total Sprint Backlog hours remaining per day

Shows the estimated amount of time to release

Ideally should burn down to zero to the end of the Sprint

Actually is not a straight line

Can bump UP

SPRINT BURN DOWN CHART

752 762

664619

304264

180

104

200

100

200

300

400

500

600

700

800

900

Re

ma

inin

g E

ffo

rt in

Ho

urs

Date

Progress

Pros & Cons

Pros Completely developed and tested features

in short iterations.

Enhanced customer and client relationships

Mistakes can be easily rectified

Easier to accommodate scope

Increasing productivity

Pros & Cons

Cons

Difficult to plan sprint

Personal cost might be higher

Task must be well defined