Agile methods

2. •
•
•
•
•
•
•
•

3. •
•
•
•
•

4. •
•
•
•
•
•

5. •
•
•
•
•
•
•
•
•

6. •
•
•
•
•

8. •
•
•
•
•
•
•
•
•
•
•
•
•
•

15. Agile Traditional
In an agile paradigm, every aspect
of development, requirements,
design, etc. is continually revisited
throughout the lifecycle.
In waterfall, development teams
only have one chance to get each
aspect of a project right.
Incremental and Iterative Linear

16. Agile Traditional
Discover the requirements by doing
the project in iterations and therefore
reducing and eliminating uncertainty
Well documented and understood
features, functions, and
requirements
Higher risk of uncertainty but
flexibility to easily adjust changes
Low risk of uncertainty and lesser
flexibility

17. Agile Traditional
Focused on budget, schedule, and
scope.
Focused on End Product
(budget and timeline are
secondary)
Trained to deliver product Command over a process

18. Agile Traditional
Requires co-location of team
members and staff in order to
embrace change and rapid produce
increments
Easily support distributed work
teams of specialists because of well
defined requirements and other
documentation
Needs experts / experienced
members
junior members are welcome

20. •
•
•

21. •
•
•
•
•

22. •
•
•
•
•
•
•
•

23. •
•
•
•

24. •
•
•
•
•

25. •
•
•
•
•
•
•
•
•
•
•
•

26. Sprint Activity
User stories
Sprint backlogProduct backlog

27. •

28. •
•
•

29. •
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

30. •
•
•
•
•
•
•
•
•
•
•
•

31. •
•
•
•
•
•
•
•
•
•
•
•
•

32. •
•
•
•
•
•

33. •
•
•
•
•
•
•
•

34. •
•
•
•
•
•

36. •
•
•
•
•
•