1. Practices and Obstacles
in Agile Development

2. Who am I?
Thorsten Suckow-Homberg, born 1976
PHP & Javascript since 1999
Sencha since 2007
Agile since 2008
working for Germany's 1st
certified Sencha Partner:
eyeworkers interactive GmbH, Karlsruhe
(jobs.eyeworkers.de)
@thorstensuckow

3. All repairs tend to destroy the structure, to increase the entropy
and disorder of the system. Less and less effort is spent on original
design flaws; more and more is spent on fixing flaws introduced by
earlier fixes. As time passes, the system becomes less and less well-
ordered. Sooner or later the fixing ceases to gain any ground. Each
forward step is matched by a backward one. Although in principle
usable forever, the system has worn out as a base for progress.

4. All repairs tend to destroy the structure, to increase the entropy
and disorder of the system. Less and less effort is spent on original
design flaws; more and more is spent on fixing flaws introduced by
earlier fixes. As time passes, the system becomes less and less well-
ordered. Sooner or later the fixing ceases to gain any ground. Each
forward step is matched by a backward one. Although in principle
usable forever, the system has worn out as a base for progress.
Frederick Brooks, The Mythical Man-Month, 1975

5. Manifesto for Agile Software Development
[...]
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
[...]
http://agilemanifesto.org

6. What exactly does „agile“ mean?
being flexible
What is the goal of being agile?
Delivering working software while adapting to
changing circumstances

7. For this talk, let's clearify:
Agile development:
SCRUM
Traditional Software Development
Waterfall Model

8. Introducing AD
to your company

9. „Start small“ vs „All-In“
choose pilot project and use it's success as an
indicator whether your company will benefit from
AD
Adapt to AD company wide overnight

10. „Going Stealth“ vs „Public Display“
stealth keeps the pressure off your team
public display proves your commitment towards AD

11. Patterns for spreading SCRUM
Split and Seed

12. Patterns for spreading SCRUM
Split and Seed
Grow and Split

13. Patterns for spreading SCRUM
Split and Seed
Grow and Split
Internal Coaching

14. Different Roles
for your Team

15. http://sarahseeandersen.tumblr.com

16. Reasons for resisting change
Lack of awareness
Fear of the unknown
Lack of job security
Fear of losing control and authority

17. New Roles
Scrum Master
Product Owner
The Team:
DB administrators
Architects
UI designer
Programmer

18. Technical Practices

19. „Later never comes.“

20. Technical Practices
Test Driven Development
Write code
Fix
compile errors
Step through
code in debugger
Repeat
(few
times
a day)
Write failing test
Write just enough
code to pass the test
Refactor
Repeat
(few
times
an hour)

21. Technical Practices
Collective Code Ownership
Avoid Knowledge Islands!

22. Technical Practices
Pair Programming (split and seed, CCO)
Refactoring
Have some spare time?
Continuous Integration

23. Thank you!

24. Resources
Books:
Succeeding with Agile, Mike Cohn, Addison Wesley
The Agile Samurai, Jonathan Rasmusson, Pragmatic Bookshelf
Scrum, Roman Pichler, dpunkt verlag
Agile Software Development, Robert C. Martin, Pearson Education
Refactoring, Martin Fowler, Addison Wesley
Continuous Integration, Paul M. Duvall, Addison Wesley