What is SCRUM

1
What is SCRUM?

• By
• Eric Zahnle

2
Purpose of Topic

• To Understand SCRUM.
• To determine if SCRUM and XP can be integrated
  successfully.
• To examine the effectiveness of SCRUM as an
  alternative to traditional development processes.

3
SCRUM

• Term scrum originally derived from strategy in
  game of rugby getting an out-of-play ball back
  into the game with teamwork. (Schwaber and
  Beedle 2002)
• First mention of Scrum in a software context,
  Wicked Problems, Righteous Solutions by DeGrace
  and Stahl, 1990.
• Jeff Sutherland first applied the concepts of
  Scrum to software development at Easel
  Corporation in 1993.

4
SCRUM aims to prevent

• Chaos due to changing requirements.
• Unrealistic estimates of time and cost.
• Lies about progression of the project.

5
SCRUM is

• Product development methodology consisting of
  practices and rules to maximize productivity.
• Empirical process that uses frequent inspection
  (daily meetings), collaboration and adaptive
  responses. (Schwaber and Beedle 2002 )
• Primarily a management tool
• Iterative and incremental
• Applicable to both small large projects

6
Elements of SCRUM

• Sprint
• Thirty calendar day iteration, four steps
• Develop/Wrap/Review/Adjust
• Backlog
• Identification of requirements.
• Sprint Backlog
• Identification of requirements for current
  iteration.
• Product Backlog
• Inventory stockpile of all requirements.

7
Elements of SCRUM(continued)

• Product Owner
• Responsible for ensuring the most important
  business value is developed first.
• SCRUM Master
• Coach and coordinator.
• Measures the process, removes impediment, leads
  the team meetings, makes decisions
• SCRUM Team
• typically not more than 9
• If more members then 9, the project should be
  broken into subprojects. In this case there
  should be people act as communication bridges
  between the teams.
• Consist of two groups pigs (working) and
  chickens (now working people, a departmental VP,
  a salesman etc.)
• working on sprint backlog

8
Elements of SCRUM(continued)

• SCRUM Meetings
• daily 15min meetings
• pigs (can talk) and chickens (cannot talk)
• is not used as a problem-solving rather
  commitments of pigs to each other
• SCRUM Master asks pigs three questions, all
  discussion other than replies
• What have you accomplished since the last
  meeting?
• Are there any obstacles in the way of meeting
  your goal?
• What will you accomplish before the next meeting?
• Release Dates - Agreed set of Sprints.

9
Scrum Cycle
10
SCRUM Sprint Cycle

• Sprint cycles of about 3-4 weeks long
• Each cycle has a theme
• Each cycle has a goal
• A potential shippable product is released at end
• Requirements are Frozen during Sprint
• Product Owner knows what the cost of the Sprint
  is
• Product Owner knows what features are expect to
  be delivered

11
SCRUM Sprint Cycle(continued)

• Starts out with a Sprint Planning Meeting
• 1 day planning meeting at beginning of Sprint
• Product Owner selects features to be implemented
  from backlogs
• Development Team discusses design
• Scrum Master attempts to identify obstacles that
  may interfere with Sprint

12
SCRUM Sprint Cycle(continued)

• During Sprint
• Daily meetings anyone can join meetings but only
  people directly involved can talk
• Daily meeting encourage productivity (a type of
  peer pressure, no wants to say they did not
  accomplish their goals from yesterday)
• Scrum Master continues to remove obstacles

13
SCRUM Sprint Cycle(continued)

• Sprint Review Meeting
• Customer meets with each Scrum Team (usually
  no more than 15 minutes per team)
• Review the Sprint
• What worked well
• What did not work well
• Areas to improve
• Etc..
• Deliver potential shippable product

14
Sounds Like XP?
15
SCRUM as a Wrapper

• SCRUM is often referred to as a wrapper because
  it does not specify software engineering
  practices.
• For example it does not define practices such as
• Pair Programming
• Test First
• Simplest Design
• Off the self parts (RAD)
• Etc.
• SCRUM simply provides a framework for such
  practices, often referred to as a
  meta-methodology.

16
SCRUM Integration(selecting engineering
practices)

• XP Because of the many similarities SCRUM and
  XP are often used together (XBreed).
• FDD Feature Driven Development
• No Practices (Not recommended)

17
Typical SCRUM / XP Integration

• SCRUM can wrap various software development
  practices such as Extreme Programming, as long as
  they support iterative development.

18
Most Common Elements of XBreed

• SCRUM
• Sprints and Sprint planning meetings
• Daily Scrums
• Product backlog and product owner
• Sprint backlog
• ScrumMaster

• XP
• Simple system design
• Test-first coding
• Continuous integration
• Refactoring
• Pair programming
• Customer Acceptance Testing

19
What about Large Projects?

• SCRUM scales well
• 800 Developers
• Distributive Environments

Example of 243 people on development team
20
Case Studies

• Project X
• Second attempt
• 4 months into project, still nothing to show
• Started SCRUM

21
Case Studies(continued)

• Primavera
• 90 Developers
• 10 Teams
• Realized they needed different engineering
  practices
• SCRUMED for 8 months before adding XP

22
Mike Cohn (User Stories Applied)
23
Conclusion

• SCRUM works because it is agile and places
  controls on process.
• Moves the development process decisions back to
  the business side.
• When combined with agile methods such as XP, can
  managed very large projects.
• SCRUM master is willing to make decisions and
  remove impediments.
• Focus on teams work.
• Project cost, final product, and completion date
  set during project Sprints.
• Knowledge transfer is high because of teamwork.

24
References

• Cohn, Mike (2004). User Stories Applied For
  Agile Software Development. Pearson Education
  Boston, MA. http//proquest.safaribooksonline.com/
  JVXSL.asp?x1modesectionsortKeyranksortOrder
  descviewsectionxmlid0321205685gcatids1b
  1f1t1c1u1ro1n1d1p1a0srchText
  
• Schwaber, Ken. Scrum development
  process. http//jeffsutherland.com/oopsla/schwapub
  .pdf
• Object Mentor, Inc. (July 2004), White Paper
  Primavera Looks for Something Better. http//www.
  controlchaos.com/download/Primavera20White20Pape
  r.pdf
• Schwaber, Ken (2001). Agile Software Development
  with Scrum. Prentice Hall.
• Advance Development Methods http//www.controlch
  aos.com
• Gulgunes Atli help develop part of this
  presentation