An Introduction to Scrum

Presented by

Wayne Allen

Large portions of this presentation of this presentation

are used w ith permission from Mike Cohn

Mountain Goat Soft ware, LL C

The Agile Manifesto–a

statement of values
Individuals
Individuals and
and over Process
Process and
and tools
tools
interactions
interactions
Comprehensive
Comprehensive
Working
Working software
software over
documentation
documentation
Customer
Customer over Contract
Contract negotiation
negotiation
collaboration
collaboration
Responding
Responding to
to over Following
Following aa plan
plan
change
change
Source: www.agilemanifesto.org

1
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.

Scrum has been used for:

• Commercial softw are • Video game development
• In-house development • FDA-approved, life-critical
systems
• Contract development
• Fixed-price projects
• Satellite-control softw are

• Financial applications
• Websites
• ISO 9001-certified
• Handheld softw are
applications • Mobile phones
• Embedded systems • Netw ork switching applications
• 24x7 systems w ith 99.999% • ISV applications
uptime requirements • Some of the largest
• the Joint Strike Fighter applications in use

2
Characteristics
• Self-organizing teams
• Product progresses in a series of month-long
“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”

Scrum 24 hours

Sprint
2-4 w eeks
Sprint goal
Return
Sprint
Potentially shippable
Cancel
Return backlog product increment
Coupons
Gift w rap
Gift
Cancel
w rap Coupons
Product
backlog

3
Putting it all together

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

4
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

Sou rce: “Th e N e w N ew Pr od uct D ev el op me nt Gam e” by

Take uc hi a nd No na ka. H arv ar d Bus in ess Rev ie w, Ja n uary
19 86.

No changes during a sprint

C hange

• Plan sprint durations around how long you

can commit to keeping change out of the
sprint

5
Scrum framework
Roles
•Product owner
•ScrumMaster
•Team Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts

Scrum framework
Roles
•Product owner
•ScrumMaster
•Team Ceremonie
s•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts

6
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

The ScrumMaster
• Represents management to the project
• Responsible for enacting Scrum values and
practices
• Removes im pediments
• Ensure that the team is fully functional and
productive
• Enable close cooperation across all roles and
functions
• Shield the team from external interferences

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

Scrum framework
Roles
•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts

8
 Team
Team
Sprint planning meeting
capacity
capacity
Sprint prioritization

Product
Product • Analy ze and evaluate product Sprint
Sprint
backlog goal
backlog
backlog
• Select sprint goal
goal
Business
Business
conditions Sprint planning
conditions
• Decide how to achieve sprint
goal (design)
Current
Current • Create sprint backlog (tasks)
Sprint
Sprint
product
product from product backlog items (user backlog
backlog
stories / features)
Technology
• Estimate sprint backlog in hours
Technology

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

9
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

Everyone answers 3 questions

1
What
What did
did you
you do
do yesterday?
yesterday?

2
What
What will
will you
you do
do today?
today?

3
Is
Is anything
anything in
in your
your way?
way?
• These are not status for the ScrumMaster
• They are commitments in front of peers

10
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

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

11
 Start / Stop / Continue
• Whole team gathers and discusses what
they’d like to:
Start
Start doing
doing

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

Scrum framework
Roles
•Product owner
•ScrumMaster
•Team Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts

12
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
This is
is the
the each sprint
product
product backlog
backlog

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
... 50

13
The sprint goal
• A short statement of what the work will be
focused on during the sprint
Life Sciences
Support features necessary for
Database Application 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.

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

14
 Tasks
Tasks Mon
Mon Tues
Tues Wed
Wed Thur
Thur Fri
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

Scalability
• Typical individual team are 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

15
Scaling through the
Scrum of scrums

Scrum of scrums of scrums

16
Where to go next
• www.mountaingoatsoftware.com/scrum
• www.scrumalliance.org
• www.controlchaos.com
• [email protected]

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

17
 .NET Tools

NUnit/MbUnit

18
TestDriven.NET

Resharper

19
NAnt
<?xml version="1.0"?>
<project name="Hello World" def ault="build" basedir=".">

<description>The Hello World of build files.</description>

<property name="debug" v alue="true" ov erwrite="f alse" />
<target name="clean" description="remov e all generated f iles">
<delete f ile="HelloWorld.exe" f ailonerror="f alse" />
<delete f ile="HelloWorld.pdb" f ailonerror="f alse" />
</target>

<target name="build" description="compiles the source code">

<csc target="exe" output="HelloWorld.exe" debug="${debug}">
<sources>
<includes name="HelloWorld.cs" />
</sources>
</csc>
</target>
</project>

Continuous Integration

CruiseControl.Net
Draco.Net
Hudson
FinalBuilder

20
NCover

NDepend

21
Simian
Similarity Analyser 2.1.2 -
http://www.redhillconsulting.com.au/products/simian/index.html
Copyright (c) 2003-04 RedHill Consulting, Pty. Ltd. All rights reserved.
Simian is not free unless used solely for non-commercial or evaluation purposes.
{ignoreCurlyBraces=true, ignoreModifiers=true, ignoreStringCase=true, threshold=9}
Loading (recursively) *.java from /var/tmp/jdksrc
Found 9 duplicate lines in the following files:
Between lines 65 and 76 in /var/tmp/jdksrc/javax/swing/plaf/basic/BasicSliderUI.java
Between lines 71 and 82 in
/var/tmp/jdksrc/com/sun/java/swing/plaf/gtk/SynthSliderUI.java
Found 9 duplicate lines in the following files:
Between lines 37 and 49 in
/var/tmp/jdksrc/com/sun/java/swing/plaf/motif/MotifCheckBoxMenuItemUI.java
Between lines 43 and 55 in
/var/tmp/jdksrc/com/sun/java/swing/plaf/motif/MotifRadioButtonMenuItemUI.java
Between lines 36 and 48 in
/var/tmp/jdksrc/com/sun/java/swing/plaf/motif/MotifMenuItemUI.java
Found 9 duplicate lines in the following files:
Between lines 391 and 435 in
/var/tmp/jdksrc/org/apache/xml/dtm/ref/DTMDocumentImpl.java
Between lines 1533 and 1577 in
/var/tmp/jdksrc/org/apache/xml/dtm/ref/dom2dtm/DOM2DTM.java
Found 9 duplicate lines in the following files:
Between lines 1744 and 1758 in
/var/tmp/jdksrc/javax/swing/plaf/metal/MetalFileChooserUI.java
Between lines 1995 and 2009 in
/var/tmp/jdksrc/com/sun/java/swing/plaf/windows/WindowsFileChooserUI.java
Between lines 849 and 863 in
/var/tmp/jdksrc/com/sun/java/swing/plaf/gtk/GTKFileChooserUI.java
Found 9 duplicate lines in the following files:
Between lines 47 and 59 in /var/tmp/jdksrc/javax/swing/plaf/basic/BasicMenuBarUI.java
Between lines 55 and 67 in
/var/tmp/jdksrc/com/sun/java/swing/plaf/gtk/SynthMenuBarUI.java

Mocking Frameworks
[TestFixture]
[ClearMocks] TypeMock
public class TestClass
{
[Test] Rhino Mocks
[VerifyMocks]
public void TestWithNatural()
{
using (RecordExpectations recorder =
NMock
RecorderManager.StartRecording())
{
ClassToIsolate.StaticMethod();
recorder.Throw(new NullReferenceException());
}
}

[Test]
[VerifyMocks]
public void TestWithReflective()
{
Mock mock = MockManager.Mock<ClassToIsolate>();
mock.ExpectAndThrow("StaticMethod", new
NullReferenceException());
}
}

22
Other Tools
• FxCop
• VS 2005/2008
• Selenium
• WatiN
• Subversion

Contact information
Presentation by: Wayne Allen
[email protected]
blogs.consultantsguild.com

Thanks to Mike Cohn f or m aking

som e of this presentation m aterial
av ailable for use by the agile
com munity.

23