Agile101 Barcamp

2,244 views
2,133 views

Published on

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

Published in: Business, Technology
1 Comment
4 Likes
Statistics
Notes
No Downloads
Views
Total views
2,244
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
95
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide

Agile101 Barcamp

  1. 1. Agile 101: an introduction 07 December 2007
  2. 2. Sandy Mamoli & Brian Calhoun
  3. 3. Agile development and project principles
  4. 4. what’s the problem?
  5. 5. what is agile?
  6. 6. what do the buzzwords mean?
  7. 7. what is it not?
  8. 8. when not to use it?
  9. 9. flavours: scrum & XP
  10. 10. conclusion
  11. 11. ready???
  12. 12. what’s the problem?
  13. 13. The writing is on the wall
  14. 14. two thirds of all projects significantly over-run on cost
  15. 15. the average project exceeds its schedule by 100%
  16. 16. 64% of the features included are rarely or never used
  17. 17. 42% of requirements change during the average project
  18. 18. how have we run projects so far?
  19. 19. requirements gathering
  20. 20. scare the crap out of them !!
  21. 21. consequences
  22. 22. ** water
  23. 23. control in waterfall is an illusion
  24. 24. software development is not like building a bridge
  25. 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. 26. what is agile?
  27. 27. simple framework with simple principles
  28. 28. about people: the team
  29. 29. about people: the client
  30. 30. about business value
  31. 31. 5 principles of agile
  32. 32. responding to change over following a plan
  33. 33. working software over comprehensive documentation
  34. 34. individuals and interactions over processes and tools Incomprehensible error Something has gone wrong Oh so very wrong Don't Save Hello What?
  35. 35. customer collaboration over contract negotiation
  36. 36. delivering the most valuable features over delivering all or the most sexy features
  37. 37. any surprises so far?
  38. 38. what do the buzzwords mean? terminology & scoping
  39. 39. “Agile” is a classification. “Waterfall” is a classification.
  40. 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. 41. what agile is NOT
  42. 42. NOT: a project methodology
  43. 43. NOT: a panacea
  44. 44. NOT: the only way
  45. 45. NOT: a reworded “code-and-fix”
  46. 46. NOT: an excuse to be lazy
  47. 47. NOT: an excuse to avoid documentation
  48. 48. NOT: an excuse to avoid planning
  49. 49. When not to use agile?
  50. 50. possibly compliance situations? “infinite” time/money, fixed features
  51. 51. agile flavours
  52. 52. Small is beautiful small cross-functional teams
  53. 53. access to client
  54. 54. product demonstrations
  55. 55. basic team values: honesty/ transparency
  56. 56. interim reviews & adaptation
  57. 57. eXtreme Programming (XP)
  58. 58. pair programming
  59. 59. “story cards” with small bits of business functionality
  60. 60. tests! unit, system, acceptance etc. manual is fine
  61. 61. optimize last
  62. 62. scrum
  63. 63. conclusion
  64. 64. happy client
  65. 65. happy team
  66. 66. high quality
  67. 67. measuring success
  68. 68. Still alive? Any questions?
  69. 69. Thank you! Sandy Mamoli sandy@scrumpractitioner.com Brian Calhoun brian@silverstripe.com

×