Presentation for weekly Salt & Pepper's lecture

1. Agile Software development

2. Agile manifesto
• Individuals and interactions over processes
and tools
• Working software over comprehensive
documentation
• Customer collaboration over contract
negotiation
• Responding to change over following a plan

3. Is Agile a replacement for
Waterfall?

4. Single pass Waterfall

5. Single pass waterfall works when
• We know the technology
• We know the domain
• We know each other

6. The Waterfall

7. “Agile”

8. The difference between Agile and
Waterfall is a length of iteration

9. The amount of the design decisions we
do before we start coding
• Human nature, Waterfall -> “Think harder”
• Agile, TDD -> “Gather feedback”
You can’t switch to Agile if you don’t
understand the difference.
You need to explain this difference to your
clients.

10. Financial aspect
• Agile -> Maximize Early Earned Value
or Cashflow or Cash on cash return
• Waterfall -> Maximize RoI

11. Agile does not define your process.
It helps you create the process that
will work for you

12. 1. Customer satisfaction by early and
continuous delivery of valuable
software

13. 2. Welcome changing requirements,
even in late development

14. 3. Working software is delivered
frequently (weeks rather than
months)

15. 4. Close, daily cooperation between
business people and developers

16. 5. Projects are built around
motivated individuals, who should
be trusted

17. 6. Face-to-face conversation is the
best form of communication (co-
location)

18. 7. Working software is the
principal measure of progress

19. 8. Sustainable development, able
to maintain a constant pace

20. 9. Continuous attention to technical
excellence and good design

21. 10. Simplicity—the art of maximizing
the amount of work not done—is
essential

22. 11. Self-organizing teams

23. 12. Regular adaptation to
changing circumstance

24. ToC an Etudes

25. Refactoring reduces cost
volatility of the next feature