This is the slide deck I used for the keynote at the Agile Open Holland Conference 2011, held November 3 & 4 in Dieren. Using this slide deck I explain about being dogmatic and religious about agile approaches, and how a lot of the lightweight approaches are not sufficient as such for most larger, more complex or enterprise projects.

1. Death by Dogma versus Agile Assembly
Sander Hoogendoorn
Principal Technology Officer & Global Agile Thoughtleader
Capgemini
@aahoogendoorn
1

2. 2

3. You would believe …
because waterfall doesn’t
work, right?

4. So the methodology doesn’t work
@aahoogendoorn They should never have used waterfall.
@aahoogendoorn Does the name of the project coincidently start with a C?

5. But how would you feel if …

6. @aahoogendoorn They didn’t apply Scrum right.
@aahoogendoorn This project likely did ScrumBut, not Scrum.
So it’s not the methodology, right?

7. 7

8. 8

9. Jack states that we have over 300 resources who are trained as SCRUM
master. As it happens I’m meeting him this afternoon. I’ll ask him.
9

10. Dogmagile

11. Crusader Agile

12.  
Scrumdamentalism

13. 
Scrumdamentalism 

14. Scrumdamentalism
 

15. Agilists against Zenifying
Just write down small things on small papers. It’s your kaizen.

16. Agilists against Zenifying
Don’t just write down small things on small papers. Write code. It’s your job.

17. There is no so thing as
one-size-fits-all agile

18. The backlog
Where does it come from?

19. And on the
seventh day
Ken created
the backlog

20. The automagical backlog

21. The automagical backlog

22. Preliminary iterations

23. Preliminary iterations

24. Preliminary iterations
Create
Stabilize
project
software
proposal
Propose Scope Realize Realize Realize Realize Finalize Manage
Write Deliver
Maintain
project working
software
plan software

25. Documentation Frenzy

26. Documentation Frenzy
 

27. But if your IT landscape looks like this …

28. Index cards might just not do the trick

29. User stories are merely meant to get the conversation going?

30. So what about documentation?

31. The agile manifesto doesn’t say
no documentation (or modeling)

32. Eventually your software will go
into maintenance (hopefully)

33. Will you document to maintain?
 

34. Guesstimation
34

35. Apples
Team 1
35

36. Apples and oranges
Team 1 Team 2
36

37. Apples and apples
Team 1 Team 2
37

38. Distributed Apples
Off
shore
Team 1 Team 2 Team 3
Team
38

39. Mandatory burn down chart?
Bad smell: note how
the same example is
used in everyone’s
presentations.
Don’t trust a vendor’s
presentation if it has
this example of a
burndown chart in it.

40. We have our ups and downs

41. Lightweight agile can be
to enterprise projects
What Monopoly is
to solving the financial crisis

42. Agile is a sliding scale
42

43. Assembling Agile

44. Assembling Agile – The basics of agile
Short Collaborative Small
Iterations Teams Unit of Work
Continuous Deliver Simplify
Planning Early & Often Communication

45. Lightweight Agile

46. Assembling Agile – Light
Short Collaborative Small
Iterations Teams Unit of Work
Continuous Deliver Simplify
Planning Early & Often Communication

47. Enterprise Agile


48. Assembling Agile – Enterprise
Short Collaborative Small
Iterations Teams Unit of Work
Continuous Deliver Simplify
Planning Early & Often Communication

49. In retrospective

50. Agile is no religion
So don’t be a zealot

51. Agile is a sliding scale
51

52. Value is found
In all agile approaces
(and yes, even in waterfall)

53. But please can we cut the crap
And go back to work?

54. 54

55. Sander Hoogendoorn
www.sanderhoogendoorn.com
@aahoogendoorn
55