SCRUM

1
SCRUM

• Randy K. Smith

2
Scrum
A play in Rugby in which the two sets of forwards
mass together around the ball and, with their
heads down, struggle to gain possession of the
ball. - www.dictionary.com
3
What is Scrum?

• Scrum is an agile process to manage and control
  development work.
• Scrum is a wrapper for existing engineering
  practices.
• Scrum is a team-based approach to iteratively,
  incrementally develop systems and products when
  requirements are rapidly changing
• Scrum is a process that controls the chaos of
  conflicting interests and needs.
• Scrum is a way to improve communications and
  maximize co-operation.

http//www.controlchaos.com/
4
What is Scrum?

• Scrum is a way to detect and cause the removal of
  anything that gets in the way of developing and
  delivering products.
• Scrum is a way to maximize productivity.
• Scrum is scalable from single projects to entire
  organizations.
• Scrum has controlled and organized development
  and implementation for multiple interrelated
  products and projects with over a thousand
  developers and implementers.
• Scrum is a way for everyone to feel good about
  their job, their contributions, and that they
  have done the very best they possibly could.

http//www.controlchaos.com/
5
Scrum Terminology

• Planning
• Develop list of features/task
• Develop time estimates
• Sprint
• Short burst of development activity to deliver
  functionality
• Time boxed (
• Daily meetings
• Feature set is fixed
• Backlog
• List of task/features dynamic reprioritized AFTER
  each Sprint
• Sprint backlog
• Product backlog
• Demo
• Demonstrate functionality from a Sprint

6
Scrum Terminology

• Product Backlog
• Dynamic
• Evolves
• Sprint Backlog
• Fixed for Sprint
• Prioritized

Product Backlog
Sprint Backlog
Sprint Backlog
Sprint Backlog
Sprint Backlog
7
Scrum Meeting

• Meeting Agenda
• What have you completed since last meeting?
• What obstacles got in your way?
• What specific things do you plan to accomplish?
• 15-30 minutes max
• Goals
• Focus on backlog items
• Communicate priorities
• Informed of obstacles and progress
• Resolve obstacles quickly
• Track progress
• Address and minimize risk

8
Scrum Teams

• Team size
• Leader
• Scrum Master
• Leads meetings
• Identifies backlog
• Empirically measures progress
• Records decisions
• Tracks items
• Reduce Risks

9
Managing Scrum
http//www.controlchaos.com/
10
Managing Scrum
Velocity of work amount of work
completed/number of days to complete work
Work Burn-down chart
http//www.controlchaos.com/
11
An Overview of Scrum
http//www.controlchaos.com/
12
Scrum

• Emphasizes
• Communications
• Teamwork
• Flexibility
• Does not focus on
• specific practices,
• specific artifacts,
• phases,
• milestones

13
Scrum is best suited for

• highly charged, independent teams of developers
• organizations that support flexible management
• Customer organization
• Developer organization
• organizations that support delivery of product
  over adherence to process
• Business Value driven organizations

14
Scrum History

• Scrum as applied to product development was first
  referred to in "The New New Product Development
  Game" (Harvard Business Review 86116137-146,
  1986)
• Later elaborated in "The Knowledge Creating
  Company" both by Ikujiro Nonaka and Hirotaka
  Takeuchi (Oxford University Press, 1995). Based
  on their ideas and research in process theory
  performed in collaboration with DuPont Advanced
  Research Facility,
• Scrum was first formulated and presented to the
  Object Management Group in 1995.
• The Scrum process is fully described in a recent
  book from Ken Schwaber and Mike Beedle, Agile
  Software Development with Scrum (Prentice Hall,
  2001).