The document discusses building bad software by focusing on time, cost, or quality alone instead of balancing all three. It then discusses agile software development which aims to fix time, cost and quality by taking an iterative approach, prioritizing user needs, and continually improving through transparency and collaboration.

1. How to build bad software

2. The problem
Strong
LightCheap

3. The problem
Strong
Light
Cheap

4. The problem
Strong
Light
Cheap

5. The problem
Strong
Light
Cheap

6. The problem
Strong
LightCheap

7. The problem
Scope
QualityTime/cost

8. The solution according to waterfall...
“Functional
Requirements
Document”
“Schedule
of work”

9. The solution according to waterfall...

10. What if you could fix time, cost AND quality?

11. The agile manifesto

12. The agile manifesto

13. As a... I want a... So I can
The ‘user story’
Member of the library An online account
Change how long I have
borrowed a book for without
going back into the library
User Feature Benefit

14. Backlog of stories
1 2 3
5 8 13
21
Sprint
Inorderofincreasingpriority

15. Sprint board

16. Pulled from
backlog into
sprint
Who is
working on it?
Stan (for the
moment)
UAT (User
Acceptance
Testing)
Fixed?
DoD
(Definition
of done)
No Yes

17. Burndown chart

18. Sprint retrospective

19. The agile manifesto

20. “I spent 15
years breeding
faster horses”

21. “focus is the art
of saying no”
MVP

22. The agile manifesto

23. The problem with FRDs and SoWs

24. Iterative development

25. The agile manifesto

26. User-centric design

27. Lean

28. “the aggregation of
marginal gains”
The new “HOT PANTS” by Team GB...

29. Iterative development

30. ● Fix time, cost and quality and compromise on none
● Transparent communication in the team
● Get to market quickly
● Respond to a changing market
“Arrive at the ‘final’ product in predictable, incremental
steps & build the right thing for the right audience”
What’s the point of Agile anyway?