Agile software development with Scrum by Vadim Izdebskiy

1. An Introduction
to Scrum
Vadim Izdebskiy
webinar @ Ciklum
2011/11/29
Mountain Goat Software,
LLC

2. Organization hints
• You can place your questions during the
webinar
• Go to «Questions» section
• Type the question and press «Send»
• This lets you ask questions at any
moment or participate in discussion,
reply my questions and etc.
Mountain Goat Software,
LLC

3. About me
Vadim Izdebskiy
• Ciklum Technical Consultant
• Certified Scrum Master
• Experienced Agile Project Manager
• Development Tools/Practices expert and coach
Vadim has more then 9 years in software development and for 5 years he is
building efficient distributed agile teams from the scratch, which are able to
deliver business value on-time and on-target using best industry practices.
Vadim is an expert in setting up development processes using Agile/Scrum,
setting up distributed communications, improving teams‘ technical
excellence, coaching best practices, introducing tools and improving
development infrastructure.
Mountain Goat Software,
LLC

4. What do we want?
Adopt Agile approach in the project
Meet the project goal effectively!
Mountain Goat Software,
LLC

5. Stages of learning
• Level 1: Shu (―obey‖)
Traditional wisdom — learning fundamentals,
techniques.
―Do this, don‘t do that‖
• Level 2: Ha ("detach", "digress")
Breaking with tradition — finding
exceptions to traditional wisdom,
reflecting on their truth, finding new ways,
techniques, and proverbs
• Level 3: Ri – ("leave", "separate―)
Transcendence — there are no techniques or proverbs, all moves are natural
• We begin from 1st level
• We can achieve next level only by practice 
Mountain Goat Software,
LLC

6. Traditional Software Development
Long, Large, Linear, Late
Time to
Market
12 to 36 months
Lifecycle Define Code Test Deploy
Tech Test Funct
Deliverables MRD PRD Code Doc Train
spec plan test
Mountain Goat Software,
LLC

7. The Project Managers
Conflict:
Successful
Project
Meet Best
Schedule Product
Granger – big cheese No Change! Edwards - Customer
Change! Conflict*
Mountain Goat Software,
LLC

8. The Project Managers Who’s to blame?
-The customer? 
Conflict: -The project manger? 
Successful -The way we build software? 
Project
Meet Best
Schedule Product
Granger – big cheese No Change! Edwards - Customer
Change! Conflict*
Mountain Goat Software,
LLC

9. Project noise level
Far from
Agreement
Anarchy
Requirements
Complex
Source: Strategic Management and
Organizational Dynamics by Ralph
Stacey in Agile Software Development
with Scrum by Ken Schwaber and Mike
Close to Simple Beedle.
Agreement
Certainty
Close to
Certainty
Far from
Technology
Mountain Goat Software,
LLC

10. We‘re losing the relay race
―The… ‗relay race‘ approach to product
development…may conflict with the goals
of maximum speed and flexibility. Instead
a holistic or ‗rugby‘ approach—where a
team tries to go the distance as a unit,
passing the ball back and forth—may
better serve today‘s competitive
requirements.‖ Hirotaka Takeuchi and Ikujiro Nonaka,
―The New New Product Development Game‖,
Harvard Business Review, January 1986.
Mountain Goat Software,
LLC

11. 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 self-
organize 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.
Mountain Goat Software,
LLC

12. Scrum origins
• Jeff Sutherland
• Initial scrums at Easel Corp in 1993
• IDX and 500+ people doing Scrum
• Ken Schwaber
• ADM
• Scrum presented at OOPSLA 96 with
Sutherland
• Author of three books on Scrum
• Mike Beedle
• Scrum patterns in PLOPD4
• Ken Schwaber and Mike Cohn
• Co-founded Scrum Alliance in 2002,
initially within the Agile Alliance
Mountain Goat Software,
LLC

13. Scrum has been used by:
•Microsoft •Intuit
•Yahoo •Nielsen Media
•Google •First American Real Estate
•Electronic Arts •BMC Software
•Lockheed Martin •Ipswitch
•Philips •John Deere
•Siemens •Lexis Nexis
•Nokia •Sabre
•IBM •Salesforce.com
•Capital One •Time Warner
•BBC •Turner Broadcasting
•Oce
Mountain Goat Software,
LLC

14. Scrum has been used for:
• Commercial software • Video game development
• In-house development • FDA-approved, life-critical
systems
• Contract development
• Fixed-price projects
• Satellite-control software
• Financial applications
• Websites
• ISO 9001-certified
• Handheld software
applications • Mobile phones
• Embedded systems • Network switching applications
• 24x7 systems with 99.999% • ISV applications
uptime requirements • Some of the largest
• the Joint Strike Fighter applications in use
Mountain Goat Software,
LLC

15. Characteristics
• Self-organizing teams
• Product progresses in a series of
two-weeks/month ―sprints‖
• Requirements are captured as items in a list of
―product backlog‖
• No specific engineering practices prescribed
• Uses generative rules to create an agile
environment for delivering projects
• One of the ―agile processes‖
Mountain Goat Software,
LLC

16. A bit of history
Lean Lean Software
Manufacturing Development
Principals Iterative
Mass Incremental
Production Development
Agile
Waterfall
Practices
RUP Scrum XP
Implementation Toyota Production Your
System team? 
1900 1950 1980 1990 2000
•1986: The New, New Product development Game
•1993: First Scrum team created by Jeff Sutherland
•1995: Scrum formalized by Jeff Sutherland & Ken Schwaber
•1999: First XP book
•2001: Agile Manifesto
•2001: First Scrum book by Ken Schwaber & Mike Beedle
•2003: Scrum alliance formed, certification program started
Mountain Goat Software,
LLC
Thanks to Henrik Kniberg

17. The Agile Manifesto–a
statement of values
Individuals and
over Process and tools
interactions
Comprehensive
Working software over
documentation
Customer
over Contract negotiation
collaboration
Responding to
over Following a plan
change
Source: www.agilemanifesto.org
Mountain Goat Software,
LLC

18. Scrum 24 hours
Sprint
2-4 weeks
Sprint goal
Return
Sprint Potentially shippable
Cancel
Return backlog product increment
Coupons
Gift wrap
Gift wrap
Cancel Coupons
Product
backlog
Mountain Goat Software,
LLC

19. Putting it all together
Image available at
www.mountaingoatsoftware.com/scrum
Mountain Goat Software,
LLC

20. Agile Software Development
Iterate, Increment and Innovate
Time to 1 to 6 months
Market
Waterfall 12 to 36 months
Waterfall Waterfall
Lifecycle
test deploy
Deliverables Working, tested code on short cycles Waterfall documentation
Mountain Goat Software,
LLC

21. Sprints
• Scrum projects make progress in a series
of ―sprints‖
• 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
Mountain Goat Software,
LLC

22. Working in an Iteration
Release Backlog
Fixed Resources
Story Card A
Story Card B
Review
Plan
Story Card C
Story Card D
Story Card …
Fixed Time
Define (Iteration)
Develop
Accept
Mountain Goat Software,
LLC

23. Sequential vs.
overlapping development
Requirements Design Code Test
Rather than doing all of
one thing at a time...
...Scrum teams do a little
of everything all the time
Source: ―The New New Product Development Game‖ by Takeuchi
and Nonaka. Harvard Business Review, January 1986.
Mountain Goat Software,
LLC

24. Incorrect Sprint Operation
DESIGN CODE TEST
SPRINT SPRINT SPRINT
Mountain Goat Software,
LLC

25. Incorrect Sprint Operation
DESIGN CODE TEST
SPRINT
Mountain Goat Software,
LLC

26. Incorrect Sprint Operation
DESIGN
CODE
TEST
Mountain Goat Software,
LLC

27. Correct Sprint Operation
DESIGN CODE TEST
SPRINT
Mountain Goat Software,
LLC

28. No changes during a sprint
Change
• Plan sprint durations around how long you
can commit to keeping change out of the
sprint
Mountain Goat Software,
LLC

29. Scrum framework
Roles
•Product owner
•ScrumMaster
•Team Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
Mountain Goat Software,
LLC

30. Scrum framework
Roles
•Product owner
•ScrumMaster
•Team Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
Mountain Goat Software,
LLC

31. Product owner
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the
product (ROI)
• Prioritize features according to market
value
• Adjust features and priority every iteration,
as needed
• Accept or reject work results
Mountain Goat
Software, LLC

32. The ScrumMaster
• Represents management to the project
• Responsible for enacting Scrum values and
practices
• Removes impediments
• Ensure that the team is fully functional and
productive
• Enable close cooperation across all roles and
functions
• Shield the team from external interferences
Mountain Goat
Software, LLC

33. The team
• Typically 5-9 people
• Cross-functional:
• Programmers, testers, user experience
designers, etc.
• Members should be full-time
• May be exceptions (e.g., database administrator)
• Teams are self-organizing
• Ideally, no titles but rarely a possibility
• Membership should change only between
sprints
Mountain Goat
Software, LLC

34. Queue theory – push vs pull Pull
Push
FIMO FIFO
First In First In
Maybe Out First Out
Mountain Goat
Software, LLC

35. Intensity
Intensity
Waterfall
Scrum
Time
Mountain Goat Software,
LLC

36. Scrum framework
Roles
•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
Mountain Goat Software,
LLC

37. Team Sprint planning meeting
capacity
Sprint prioritization
Product • Analyze and evaluate product Sprint
backlog backlog goal
• Select sprint goal
Business
conditions Sprint planning
• Decide how to achieve sprint
Current goal (design) Sprint
product • Create sprint backlog (tasks)
from product backlog items backlog
(user stories / features)
Techno- • Estimate sprint backlog in hours
logy
Mountain Goat
Software, LLC

38. 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
As a vacation Code the middle tier (8 hours)
planner, I want to Code the user interface (4)
see photos of the Write test fixtures (4)
hotels.
Code the foo class (6)
Update performance tests (4)
Mountain Goat
Software, LLC

39. The daily scrum
• Parameters
• Daily
• 15-minutes
• Stand-up
• Not for problem solving
• Whole world is invited
• Only team members, ScrumMaster, product
owner, can talk
• Helps avoid other unnecessary meetings
Mountain Goat
Software, LLC

40. Everyone answers 3 questions
1
What did you do yesterday?
2
What will you do today?
3
Is anything in your way?
• These are not status for the ScrumMaster
• They are commitments in front of peers
Mountain Goat
Software, LLC

41. The sprint review
• Team presents what it accomplished
during the sprint
• Typically takes the form of a demo of new
features or underlying architecture
• Informal
• 2-hour prep time rule
• No slides
• Whole team participates
• Invite the world
Mountain Goat
Software, LLC

42. Sprint retrospective
• Periodically take a look at what is and is
not working
• Typically 15–30 minutes
• Done after every sprint
• Whole team participates
• ScrumMaster
• Product owner
• Team
• Possibly customers and others
Mountain Goat
Software, LLC

43. Start / Stop / Continue
• Whole team gathers and discusses what
they‘d like to:
Start doing
Stop doing
This is just one
of many ways to Continue doing
do a sprint
retrospective.
Mountain Goat
Software, LLC

44. Scrum framework
Roles
•Product owner
•ScrumMaster
•Team Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
Mountain Goat
Software, LLC

45. Product backlog
• The requirements
• A list of all desired work on
the project
• Ideally expressed such that
each item has value to the
users or customers of the
product
• Prioritized by the product
owner
• Reprioritized at the start of
This is the each sprint
product backlog
Mountain Goat Software,
LLC

46. Working in a Release
Product Backlog Release A: Features 1, 2, 3
Iteration 1 Iteration 2 Iteration 3
Feature 1
Feature 2
Review
Review
Feature 3
Review
Review
Plan
Plan
Plan
Plan
Feature 4
Feature 5
Feature 6…
Mountain Goat Software,
LLC

47. A sample product backlog
Backlog item Estimate
Allow a guest to make a reservation 3
As a guest, I want to cancel a
5
reservation.
As a guest, I want to change the dates of
3
a reservation.
As a hotel employee, I can run RevPAR
8
reports (revenue-per-available-room)
Improve exception handling 8
... 30
...
Mountain Goat Software, 50
LLC

48. The sprint goal
• A short statement of what the work will be
focused on during the sprint
Life Sciences
Support features necessary
Database Application for population genetics studies.
Make the application run on
SQL Server in addition to
Oracle. Financial services
Support more technical
indicators than company ABC
with real-time, streaming data.
Mountain Goat Software,
LLC

49. Managing the sprint backlog
• Individuals sign up for work of their own choosing
• Work is never assigned
• Estimated work remaining is updated daily
• Any team member can add, delete or change the
sprint backlog
• Work for the sprint emerges
• If work is unclear, define a sprint backlog item with
a larger amount of time and break it down later
• Update work remaining as more becomes known
Mountain Goat Software,
LLC

50. A sprint backlog
Tasks Mon Tues Wed Thur Fri
Code the user interface 8 4 8
Code the middle tier 16 12 10 4
Test the middle tier 8 16 16 11 8
Write online help 12
Write the foo class 8 8 8 8 8
Add error logging 8 4
Mountain Goat Software,
LLC

51. A sprint burndown chart
Mountain Goat
Software, LLC

52. Tasks Mon Tues Wed Thur Fri
Code the user interface 8 4 8
Code the middle tier 16 12 10 7
Test the middle tier 8 16 16 11 8
Write online help 12
50
40
30
Hours
20
10
0
Mon Tue Wed Thu Fri
Mountain Goat
Software, LLC

53. Scalability
• Typical individual team is 7 ± 2 people
• Scalability comes from teams of teams
• Factors in scaling
• Type of application
• Team size
• Team dispersion
• Project duration
• Scrum has been used on multiple 500+
person projects
Mountain Goat
Software, LLC

54. Scaling through the
Scrum of scrums
Mountain Goat
Software, LLC

55. Scrum of scrums of scrums
Mountain Goat
Software, LLC

56. Where to go next
• http://mountaingoatsoftware.com/scrum
• http://scrumalliance.org
• http://controlchaos.com
Mountain Goat Software,
LLC

57. A Scrum reading list
• Agile and Iterative Development: A Manager’s Guide by
Craig Larman
• Agile Estimating and Planning by Mike Cohn
• Agile Project Management with Scrum by Ken Schwaber
• Agile Retrospectives by Esther Derby and Diana Larsen
• Agile Software Development Ecosystems by Jim Highsmith
• Agile Software Development with Scrum by Ken Schwaber
and Mike Beedle
• Scrum and The Enterprise by Ken Schwaber
• User Stories Applied for Agile Software Development by
Mike Cohn
• Lots of weekly articles at www.scrumalliance.org
Mountain Goat Software,
LLC

58. Copyright notice
• You are free:
• to Share―to copy, distribute and transmit the work
• to Remix―to adapt the work
• Under the following conditions
• Attribution. You must attribute the work in the manner
specified by the author or licensor (but not in any way that
suggests that they endorse you or your use of the work).
• Nothing in this license impairs or restricts
the author‘s moral rights.
• For more information see
http://creativecommons.org/licenses/by/3.0/
Mountain Goat Software,
LLC