This document discusses the history and principles of agile development. It outlines how agile practices emerged in response to flaws with traditional waterfall development models. The agile manifesto values individuals and interactions, working software, customer collaboration, and responding to change over processes, tools, documentation, and following a plan. Common agile practices like scrum, extreme programming, and kanban are discussed. The document emphasizes that agile is about quality, teams, and individuals rather than processes alone. It concludes that truly being agile is more important than just doing agile activities.

1. The Why Beneath the What
@arsagilis

2. “ Plans are
useless, but
planning is
everything ”
US President Edward D. Eisenhower, 1957
@arsagilis

3. About me
Change Agent
Teaching
Agile
RoR developer
Agile since 2001 1st site at the age of 14
Certified Scrum Master
LAMP
PhotoBox
Agile UX
Passionate Kanban
FOSS enthusiast Drupal Certified Scrum Professional
PHP developer Amnesty International
Scrum
@arsagilis

4. What is Agile about?
 Welcoming change
 Quality of products
 Great software is a product of
great teams
 Great teams are a product of
individuals, not process

5. Before agile
@arsagilis
Winston Royce, 1970

6. Winston Royce on Waterfall
“ ... The implementation
described above is
risky and invites
failure.
”
Winston Royce, 1970
@arsagilis

7. Before agile
le -
pe op !
t th e E S S
t’s no O C
I P R
t he
it’s
@arsagilis
Winston Royce, 1970

8. @arsagilis
2001 http://agilemanifesto.org

9. O P LE
ut PE ary
L a bo co nd
A L is se
s The first statement
It’ ce ss
p o
rstresses people
-
@arsagilis

10. Yoda says ...
Great
people,
building great
teams they do
Great
products they
Master Yoda, 2012 in turn create!
@arsagilis

11. The A-Team says ...
Great
teams
create great
products!
Great teams
are made of
great people
@arsagilis

12. Does the “Why?” matter?
Every action
needs a
reason or it
is irrelevant!
Master Pai Mai, 2003
@arsagilis

13. Many agile practices
 Scrum
 eXtrememe Programming
 Dynamic Systems Development Method
 Crystal Clear
 Feature-Driven Development
 Kanban
 Test-Driven Development
 Behaviour-Driven Development
@arsagilis

14. Agile Manifesto
Individuals and
over Process and tools
interactions
Comprehensive
Working software over
documentation
Customer Contract
over
collaboration negotiation
Responding to
over Following a plan
change
@arsagilis

15. Five XP Values
Communication
Simplicity
Feedback
Courage
Respect
@arsagilis

16. Five Scrum Values
Courage
Commitment
Respect
Openness
Focus
@arsagilis

17. Agile Practices
Agile Manifesto 5 Scrum Values
5 XP Values
Based on Reliant upon
Agile Practices
@arsagilis

18. Daily stand-up
Based on Reliant upon
Individuals and Interactions Courage
Customer collaboration Commitment
Responding to change Openness
Sprint Planning
Based on Reliant upon
Individuals and Interactions Courage
Working software Commitment
Responding to change Focus
@arsagilis

19. Sprint review
Based on Reliant upon
Individuals and Interactions Courage
Customer collaboration Commitment
Working software Openness
Retrospective
Based on Reliant upon
Individuals and Interactions Courage
Customer collaboration Respect
Responding to change Commitment
@arsagilis

20. Also important values
Rapid feedback High-quality features
BDD (A)TDD
CI Pair programming
XP etc.
@arsagilis

21. Yoda says ...
Half-arsed
solutions,
don’t do!
Master Yoda, 2012
@arsagilis

22. When Agile is doomed to
fail
2010 http://www.halfarsedagilemanifesto.org

23. Conclusion
Being
agile,
more
important
than doing
agile, is!
@arsagilis Master Yoda, 2012

24. Any Questions?
Michael Chik
mchik@macmillan.org.uk
Twitter: @arsagilis
Skype: michael.chik
linkedin.com/in/michaelchik