Your SlideShare is downloading. ×
Scrum Workshop - Agile Presentation March 18, 2012
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum Workshop - Agile Presentation March 18, 2012

714
views

Published on

Agile P

Agile P

Published in: Technology

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
714
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
30
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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