SCRUM

SCRUM is
a simple iterative and
incremental process framework
that can be applied to develop any
kind of product and to manage
any kind of complex activity.

Scrum helps to
find and show
problems

Scrum helps to
find and show
problems

BUT

Scrum does not fix any

of them

Scrum does not fix any

of them
WE need to fix them

Scrum Flow

Who uses Scrum :

Google
Yahoo!
Microsoft
Electronic Arts
Lockheed Martin
Philips
Siemens
Nokia
BBC
Nielsen Media
SalesForce.com
Oracle
Time Warner
Turner Broadcasting
Toyota
BMC Software
Capital One

Key Characteristics
Delivery Focus

Key Characteristics
Delivery Focus
Transparency

Key Characteristics
Delivery Focus
Transparency
Short and fixed cycles (10 working days)

Key Characteristics
Delivery Focus
Transparency
Short and fixed cycles (10 working days)
Total Quality

Key Characteristics
Delivery Focus
Transparency
Short and fixed cycles (10 working days)
Total Quality
Team Work (cross functional)

Key Characteristics
Delivery Focus
Transparency
Short and fixed cycles (10 working days)
Total Quality
Team Work (cross functional)
Constant Communication

Key Characteristics
Delivery Focus
Transparency
Short and fixed cycles (10 working days)
Total Quality
Team Work (cross functional)
Constant Communication
Commitment

Key Characteristics
Delivery Focus
Transparency
Short and fixed cycles (10 working days)
Total Quality
Team Work (cross functional)
Constant Communication
Commitment
Self organization

Key Characteristics
Delivery Focus
Transparency
Short and fixed cycles (10 working days)
Total Quality
Team Work (cross functional)
Constant Communication
Commitment
Self organization
Reveals the problems

3 ROLES :
Product Owner
Scrum Master
The Team

PRODUCT OWNER
Define & explain the backlog for the team to
understand
Manage & prioritizes work based on
Business Value
Negotiates work with team
Available to answer questions to the team
Interact with client to define the Product
Backlog
Manages client issues
Participates in standups, demos, retros &
plannings

PRODUCT OWNER
Product Backlog is not visible
Too big stories
More than 1 PO
Backlog doesnt prioritized
effectively/constantly
PO doesnt participates in any scrum
meeting
PO doesnt manages client issues

SCRUM MASTER
Protect values & principles of Scrum
Identified & Remove Impediments
Negotiates work with team
Keep the team fully functional & productive
Keep the team focused on delivery
Maintained the Scrum Board
Facilitates & improve dynamics to reveal
problems
Shield the team from dark forces
Does NOT allocate the tasks

SCRUM MASTER
Not keeping Scrum process on track

Letting the technical discussion on

standup
SM act like a Tech Guru
SM doesnt have impediment
SM doesnt participates in any
scrum meeting

THE TEAM
Typically 5-9 people
Cross-functional members
Frequently communicating
Self-organized
Estimates complexity
Negotiate work with the PO
Work result should meet ALL
Acceptance Criteria

THE TEAM
Fixed Roles
Too many team members

Never-ending discussion on standup

Not helping each other
Implementing all stories in parallel

PIGS VS CHICKENS

3 CEREMONIES
Sprint Planning
Daily Scrum
Review &
Retrospective

Sprint Planning:
PO present sprint goal & describes each stories
Team should have clearly understand about
the stories
Team estimates complexity of every stories
planning poker

Establishing who has vacation time on upcoming

sprint

Team define the tasks for every stories

Daily Standup:
Attending by PO-SM-Team, the others count as a
chicken
Goals : Improvement, Focus, Communication
Scheduled in the same time every day
Max 15-20mins
NO Never-ending discussion
Patterns : 1. What did I accomplish yesterday
2. What will I do today?
3. What obstacles are impending my
progress?

Update the scrum board

Review &
Retrospective:
Review (Demo) Teams showing their
accomplishment
Informal .pptx, notes
Only PIGS can talk
Retrospective: - (GLAD) What was cool?
- (SAD) What can we
improve?
- (MAD) What went wrong?
Facilitate by SM
Analyze & discuss the problem

3 ARTIFACTS
Product Backlog
Sprint Backlog
Burndown Chart

PRODUCT BACKLOG
Product requirements
Ordered by PO based on business
value, risk, dependencies, date needed
A list of Ideas, Features
Estimated by the Team
Expressed in the form of User
Stories

User Stories

Simple & concise

Easy to understand
Have Acceptance Criteria / Minimum
Requirement
Estimated by The Team Complexity
points

Format: Who? What? Why? As a

[role], I
want to be able to [feature], so
that/because

SPRINT BACKLOG
List of work for The Team for the
next sprint
Prioritized by PO
Estimated by the Team
Broken down into tasks by The
Team
Promotes self-organization of the
Team
Expressed in the form of User

Burn Down Chart

Provides visibility into
the Sprint
Illustrated progress by
the Team
Ideal effort as a
guideline

Samples of Burndown

Samples of Burndown

Samples of Burndown

Definition of Done
DONE or NOT DONE
Avoid the 90% Syndrome
Peer reviewed (or produce w/ pair
programming)
Builds without errors (Continuous
Integration)
Unit test written and passing (TDD)

Deployed to test environment and passed

on all test