Scrum Day Twin Cities 2015

1. Tell me again, why are we doing
this agile thing?
Or, what it means to deliver
real value…
Scrum Day Twin Cities 2015
Paul Ellarby

3. What is the agile value proposition?

4. Build the Right Thing

5. 1
2
63%
27%
Functionality that is never
or rarely used

6. If you spend 3 months building the perfect specification document…
…you just wasted 3 months of your life that you will never get back.

7. Assumptions Challenged!
• 3 things we wish were true
• The customer knows what the want
• The developers know how to build it
• Nothing will change along the way
3 things we have to live with
• The customer discovers what the want
• The developers discover how to build it
• Many things change along the way
Source: Henrik Kniberg

8. Business Drives Development
• Scrum considers this a good thing.
• Because of this, a closer relationship between
business professionals and technologists exists
than was typical before.
• Thus, we need to consider the dilemmas
we are likely to experience when
“Business Drives Development.”

9. Don’t really now what we want until
we see it…
Customers loved this… Until they tried this…

10. Elop – Stephen Elop, former Nokia CEO and Microsoft VP

11. IBM
Agile vs. not-so agile

12. Decision to implement
company-wide scrum
Pega Systems

13. Source: Jeff Sutherland, Scrum Inc

14. Agile View
Assess
Identify
partial
concepts
• Agile View of Product Management

15. Incremental Delivery = More ValueValue
Time / Cost / Features
Stop the
project!

16. Responding
to change
Delight the
customer
Working
product
Great
teams
Agile
Manifesto

19. Leadership
Strategic
Vision
Customer
First
Support the
Teams
Shipping
Product

22. Build the Thing Right

23. Engineering Practices
• Unit Testing and Test Driven Development
• Pairing
• Refactoring
• Continuous Integration

24. Unit Test
• Is usually done by developers
• Improves quality
• Facilitates changes
• Simplifies integration
• Enables automation
• Provides effective system documentation
• Makes your life simpler
“A Unit Test is a procedure used to validate that individual
units of functional code are working properly. “

25. Unit Testing
The Agile Way: Test First

26. Test Driven Development
“Test-Driven Development (TDD) is an
evolutionary approach to development which
instructs you to have test-first development
intent. Basically, you start by writing a test and
then you code to elegantly fulfill the test
requirements.”
• Small successful, tested steps.
• Do the simplest thing that could possibly work.

27. Copyright 2009 ThoughtWorks
A User Story

28. Copyright 2009 ThoughtWorks
Test First

29. Copyright 2009 ThoughtWorks

30. Copyright 2009 ThoughtWorks

31. Copyright 2009 ThoughtWorks

32. Uncle Bob Martin’s Three Laws of TDD
1. You are not allowed to write any production
code unless it is to make a failing unit test
pass.
2. You are not allowed to write any more of a
unit test than is sufficient to fail; and
compilation failures are failures.
3. You are not allowed to write any more
production code than is sufficient to pass the
one failing unit test.

33. Pairing

34. Refactoring

35. Practically Speaking..
What is Refactoring?
• Verify no change in external behavior by
– Testing
– Being very, very careful
A series of small steps, each of which changes the program’s
internal structure without changing its external behavior

36. Why Refactor
• To make room for new functionality
• To make the program easier to change
• To make the software easier to understand
• To “Fix broken windows”

37. “Continuous Integration is a software development
practice where members of a team integrate their work
frequently, usually each person integrates at least daily -
leading to multiple integrations per day. Each integration is
verified by an automated build (including test) to detect
integration errors as quickly as possible. Many teams find
that this approach leads to significantly reduced integration
problems and allows a team to develop cohesive software
more rapidly.”
http://www.martinfowler.com/articles/continuousIntegration.html

38. How much to automate?
Answer: It depends!

39. Tell me again, why are we doing
this agile thing?