Successfully reported this slideshow.
Introduction to                                 AgileAgile Vietnam – Scrum WorkshopSunday March 18, 2012
1   What is Agile?2   Why Agile?3   How Long to Learn?
“To be competitive, organizations need to drive innovation inevery part of their business”
What isAgile?
It is a mindset foreffectively completing         projects.
DUH !
Common Sense      YesCommon Practice   No
Agile MethodsXP     SCRUM      CrystalFDD     Lean      DSDM
Common CharacteristicsIterative DevelopmentCross-Functional & Self-Organized TeamFace-to-Face Communication vs. DocumentsO...
Why Agile?
Traditional Approach to    managing SoftwareDevelopment Projects failing        far too often
Why it Fails?
Traditional Methodology istoo heavy and bureaucratic
Difficult to remain competitive
Example of Failures
Cloud Notes Inc.Anytime, Anywhere, post it!
Two major reasons for failure:         Disappointing features      Poor Interfaces cause failure
What are we learning here?
Success is not justfunctionality anymore
Example of Success
How many features?
1
What are we learning?Features are not that important
What’s more important?      Usability   User Experience
Why use Agile Methods?
Incremental Approachbreaks complex projects    down into simple      mini-projects
AccommodatesChange Easily
Improve ROI
Able to deliver quicklyChange oftenMitigate riskInvolve customerUltimate freedomUltimate responsibility
Increase Business ValueLower Development RiskHigher QualityLess DefectsEmployee EngagementTrust in People…
How Longto Learn?
Few hours to learn,Life time to mastered
Conclusion:
Agile ApproachAdaptive, empirical process• Small repeating cycles• Short-term planning with constant feedback, inspection ...
Agile ManifestoDriven by technical forces, the Agile Manifesto wascreated on February 2001
Do you know the most common Agile Method?
Team that get it right, 1 Extra Bonus Point
Agile is NOT a magic bulletEach situation its approach   Mastered by practice
Thank you for listeningagile@agilevietnam.org
Scrum Workshop - Agile Presentation March 18, 2012
Upcoming SlideShare
Loading in …5
×

Scrum Workshop - Agile Presentation March 18, 2012

1,053 views

Published on

Agile P

Published in: Technology
  • Be the first to comment

Scrum Workshop - Agile Presentation March 18, 2012

  1. 1. Introduction to AgileAgile Vietnam – Scrum WorkshopSunday March 18, 2012
  2. 2. 1 What is Agile?2 Why Agile?3 How Long to Learn?
  3. 3. “To be competitive, organizations need to drive innovation inevery part of their business”
  4. 4. What isAgile?
  5. 5. It is a mindset foreffectively completing projects.
  6. 6. DUH !
  7. 7. Common Sense YesCommon Practice No
  8. 8. Agile MethodsXP SCRUM CrystalFDD Lean DSDM
  9. 9. Common CharacteristicsIterative DevelopmentCross-Functional & Self-Organized TeamFace-to-Face Communication vs. DocumentsOpen Office vs. Cubicles
  10. 10. Why Agile?
  11. 11. Traditional Approach to managing SoftwareDevelopment Projects failing far too often
  12. 12. Why it Fails?
  13. 13. Traditional Methodology istoo heavy and bureaucratic
  14. 14. Difficult to remain competitive
  15. 15. Example of Failures
  16. 16. Cloud Notes Inc.Anytime, Anywhere, post it!
  17. 17. Two major reasons for failure: Disappointing features Poor Interfaces cause failure
  18. 18. What are we learning here?
  19. 19. Success is not justfunctionality anymore
  20. 20. Example of Success
  21. 21. How many features?
  22. 22. 1
  23. 23. What are we learning?Features are not that important
  24. 24. What’s more important? Usability User Experience
  25. 25. Why use Agile Methods?
  26. 26. Incremental Approachbreaks complex projects down into simple mini-projects
  27. 27. AccommodatesChange Easily
  28. 28. Improve ROI
  29. 29. Able to deliver quicklyChange oftenMitigate riskInvolve customerUltimate freedomUltimate responsibility
  30. 30. Increase Business ValueLower Development RiskHigher QualityLess DefectsEmployee EngagementTrust in People…
  31. 31. How Longto Learn?
  32. 32. Few hours to learn,Life time to mastered
  33. 33. Conclusion:
  34. 34. Agile ApproachAdaptive, empirical process• Small repeating cycles• Short-term planning with constant feedback, inspection and adaptation Scope Evaluate Define Develop
  35. 35. Agile ManifestoDriven by technical forces, the Agile Manifesto wascreated on February 2001
  36. 36. Do you know the most common Agile Method?
  37. 37. Team that get it right, 1 Extra Bonus Point
  38. 38. Agile is NOT a magic bulletEach situation its approach Mastered by practice
  39. 39. Thank you for listeningagile@agilevietnam.org

×