Agile 101 presentation from the recent Agile barcamp held in Wellington on 7 December 2007. Co-presented with Sandy Mamoli.

1. Agile 101: an
introduction
07 December 2007

2. Sandy Mamoli & Brian Calhoun

3. Agile development and project
principles

4. what’s the problem?

5. what is agile?

6. what do the buzzwords mean?

7. what is it not?

8. when not to use it?

9. flavours: scrum & XP

10. conclusion

11. ready???

12. what’s the problem?

13. The writing is on the wall

14. two thirds of all projects
significantly over-run on cost

15. the average project exceeds its
schedule by 100%

16. 64% of the features included are
rarely or never used

17. 42% of requirements change
during the average project

18. how have we run projects so far?

19. requirements gathering

20. scare the crap out of them !!

21. consequences

22. ** water

23. control in waterfall is an illusion

24. software development is not like
building a bridge

25. let’s accept reality:
software dev is unpredictable
don’t kill trees to manage risk
must deal with change
must have no surprises

26. what is agile?

27. simple framework with simple
principles

28. about people: the team

29. about people: the client

30. about business value

31. 5 principles of agile

32. responding to change over
following a plan

33. working software over
comprehensive documentation

34. individuals and interactions over
processes and tools
Incomprehensible error
Something has gone wrong
Oh so very wrong
Don't Save Hello What?

35. customer collaboration over
contract negotiation

36. delivering the most valuable
features over delivering all or the
most sexy features

37. any surprises
so far?

38. what do the buzzwords mean?
terminology & scoping

39. “Agile” is a classification.
“Waterfall” is a classification.

40. Agile
- indviduals over processes
- working software over documentation
- customer collaboration over contract negotiation
- responding to change over following a plan
Methods
eXtreme
Programming DSDM
Scrum
Crystal
others...
FDD

41. what agile is NOT

42. NOT: a project methodology

43. NOT: a panacea

44. NOT: the only way

45. NOT: a reworded “code-and-fix”

46. NOT: an excuse to be lazy

47. NOT: an excuse to avoid
documentation

48. NOT: an excuse to avoid planning

49. When not to use agile?

50. possibly compliance situations?
“infinite” time/money, fixed
features

51. agile flavours

53. Small is beautiful
small cross-functional teams

54. access to client

55. product demonstrations

56. basic team values: honesty/
transparency

57. interim reviews & adaptation

58. eXtreme Programming (XP)

59. pair programming

60. “story cards” with small bits of
business functionality

61. tests! unit, system, acceptance
etc.
manual is fine

62. optimize last

63. scrum

65. conclusion

66. happy client

67. happy team

68. high quality

69. measuring success

70. Still alive? Any questions?

71. Thank you!
Sandy Mamoli
sandy@scrumpractitioner.com
Brian Calhoun
brian@silverstripe.com