Agile is a mindset for effectively completing projects using an iterative and incremental approach. It is becoming more commonly used as traditional project management approaches are often too heavy and bureaucratic, making it difficult for organizations to remain competitive. Agile methods like Scrum, XP, and Crystal break large projects into smaller iterative cycles, accommodate frequent changes, improve return on investment, and involve customers for higher quality outputs. While only taking a few hours to learn the basics, Agile is a lifetime framework to master, with an emphasis on adaptive planning, empirical learning, and frequent inspection and adaptation of processes.

1. Introduction to
Agile
Agile Vietnam – Scrum Workshop
Sunday 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 in
every part of their business”

4. What is
Agile?

5. It is a mindset for
effectively completing
projects.

6. DUH !

7. Common Sense Yes
Common Practice No

8. Agile Methods
XP SCRUM Crystal
FDD Lean DSDM

9. Common Characteristics
Iterative Development
Cross-Functional & Self-Organized Team
Face-to-Face Communication vs. Documents
Open Office vs. Cubicles

10. Why Agile?

11. Traditional Approach to
managing Software
Development Projects failing
far too often

12. Why it Fails?

13. Traditional Methodology is
too 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 just
functionality 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 Approach
breaks complex projects
down into simple
mini-projects

27. Accommodates
Change Easily

28. Improve ROI

29. Able to deliver quickly
Change often
Mitigate risk
Involve customer
Ultimate freedom
Ultimate responsibility

30. Increase Business Value
Lower Development Risk
Higher Quality
Less Defects
Employee Engagement
Trust in People
…

31. How Long
to Learn?

32. Few hours to learn,
Life time to mastered

33. Conclusion:

34. Agile Approach
Adaptive, empirical process
• Small repeating cycles
• Short-term planning with constant feedback, inspection and
adaptation
Scope
Evaluate Define
Develop

35. Agile Manifesto
Driven by technical forces,
the Agile Manifesto was
created on February 2001

36. Do you know the
most common
Agile Method?

37. Team that get it right,
1 Extra Bonus Point

39. Agile is NOT a magic bullet
Each situation its approach
Mastered by practice

40. Thank you for listening
agile@agilevietnam.org