agile vs. traditional methodologies
•
1 like•3,189 views
These slides generally are about to find the major differences between the two major software development methods - traditional and agile methods. Also some brief review about these two methods will be presented. But the major focus is on comparison between them.
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (10)
Similar to agile vs. traditional methodologies
Similar to agile vs. traditional methodologies (20)
Recently uploaded
Recently uploaded (20)
agile vs. traditional methodologies
- 1. Agile vs. Traditional methodologies By : Morteza Bandidarian Bogazici university – SWE department fall 2014
- 2. Traditional Methodologies Agenda • Traditional methodologies • Agile methodologies • Compare and contrast • Which one to choose?
- 3. Traditional Methodologies Requirements Design Implementation Verification Maintenance Waterfall Model Requirements Specification Document Design Specification Document Working product + source code + manuals
- 4. Agile Methodologies Agenda • Traditional methodologies • Agile methodologies • Compare and contrast • Which one to choose?
- 5. Agile Methodologies Agile manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Agile manifesto’s value: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiations • Responding to change over following the plan
- 6. Agile Methodologies • Agile development is based on the idea of incremental and iterative development. It iteratively improves software by using customer feedback to converge on solutions • There is no pre defined plan. • All of works start at the same time when project starts
- 7. Compare and Contrast Agenda • Traditional methodologies • Agile methodologies • Compare and contrast • Which one to choose?
- 8. Compare and Contrast Waterfall Model Advantages: Documentation and structured design, when new members join the team It is easy to understand and use It is easy to coordinate due to model’s rigidity Stages are completed in sequence not parallel It is recommended for large projects Disadvantages: Some new requirements may arise just after requirements gathering is finished, and negatively affect the project It is difficult for each stage to estimate time and budget required for each stage There is no working product until the SDLC ends If some defects and bugs found in testing, it is hard to track them and go back to design or development stage There is high risk and uncertainty
- 9. Compare and Contrast Waterfall Model Rarely 19% Never 45% Always 7% Often 13% Sometimes 16% 64% implemented features are rarely or never used
- 10. Compare and Contrast Agile difficulties • Enormous reduction of documentation • so it is hard for new comers to understand the project and complete tasks • Some architectural problems may happen and not being found easily • New comers: they asks lots of questions from senior developers and may delay completion of iteration which means increased project cost • it is not suitable for life-critical systems. [Boehm, Scott Ambler] • agile methods provide workable solutions only for “business software” [Martin Fowler] • Needs high-skilled staff (technically, socially etc.), while 49.999 percent of world’s developers are below average [Boehm]
- 11. Compare and Contrast Major differences: Agile methods emphasize on teams, working software, customer collaboration, and responding to change; while the conventional methods stress on contracts, plans, processes, documents, and tools.
- 12. Compare and Contrast Traditional development Agile development Fundamental Hypothesis Systems are fully specifiable and predictable, and are developed through detailed planning High quality adaptive software is developed by small teams That use the principle of continuous improvement based on Fast feedback and change Management style Command and control Leadership and collaborative Knowledge management Explicit Implicit Communication Formal Informal Development model Life cycle Model Evolutionary model Organization structure Mechanic (bureaucratic, high formalization) – suits large sized organizations Organic (flexible and participative, encourages social cooperation)– suits small/medium sized organizations Quality control Difficult planning and strict control. Difficult and late testing Permanent control and testing
- 13. Compare and Contrast Traditional development Agile development User requirements Detailed and defined before coding Interactive coding Testing After coding is completed Every iteration Client involvement Low High Additional abilities required from developers Nothing Interpersonal abilities, and basic knowledge of the business Scale of project and team Large Small and medium Requirements Must be stable and known in advance Emergent, with rapid changes Architecture Design for all predicted requirements Design for current requirements
- 14. Compare and Contrast 24-Dec-14 Waterfall Agile : Iterative Development Upfront, Detailed Emergent Design Linear hand-offs: Dev then QA Cross-functional & collaborative: Dev & QA Formal process, implemented at end Welcomed, prioritized vs. backlog At beginning and at delivery Throughout cycle Teamwork Change Requests Customer / User Involvement Specifications Scrum is the most popular Agile method: 74% of Agile practitioners (2009)
- 15. Compare and Contrast Surveys of Agile Methods Rico, D. F. (2008). What is the return-on-investment of agile methods? Retrieved February 3, 2009, from http://davidfrico.com/rico08a.pdf
- 16. Compare and Contrast Productivity of Agile Methods PP productivity 32X more than trad. methods Scrum productivity 5X more than trad. Methods Agile methods productivity 20X more than traditional Rico, D. F., Sayani, H. H., & Sone, S. (2009). The business value of agile methods. Ft. Lauderdale, FL: J. Ross Publishing
- 17. Compare and Contrast Quality of Agile Methods XP quality 13X better than trad. Methods Scrum quality 3X better than trad. Methods Agile methods quality 5X better than traditional Rico, D. F., Sayani, H. H., & Sone, S. (2009). The business value of agile methods. Ft. Lauderdale, FL: J. Ross Publishing
- 18. Compare and Contrast Costs of Agile Methods XP costs 8X less than traditional methods Scrum costs 2X less than traditional methods Agile methods cost 5X less than traditional methods Rico, D. F., Sayani, H. H., & Sone, S. (2009). The business value of agile methods. Ft. Lauderdale, FL: J. Ross Publishing
- 20. Which one to choose Agenda • Traditional methodologies • Agile methodologies • Compare and contrast • Which one to choose?
- 21. Which one to choose Agile innovation Waterfall cookbook Requirements (emergent) Change (frequent) Experience (mixture of juniors and seniors) Resource dedication Resources physical location (not dedicated) Customer involvement (low) Timelines (strict time lines) Documentation (low) With these situations Agile is the best option for the company
- 22. References References: 1. ISSUES AND CHALLENGES OF AGILE SOFTWARE DEVELOPMENT WITH SCRUM 2. Agile manifesto, http://agilemanifesto.org/ 3. Software Development Life Cycle AGILE vs Traditional Approaches 4. Project Management Practices: The Criteria for Success or Failure 5. Agile Software Development: It’s about Feedback and Change 6. Using risk to balance agile and plan-driven methods 7. Software Development: Agile vs. Traditional 8. http://www.youtube.com/watch?v=jL1VOF5JgPQ
- 23. Thanks for your attention