Software Delivery Methodologies: Agile and Waterfall Patterns July 8, 2009 IowAccess Advisory Council

Goals and Overview Context of the discussion Key Attributes of Waterfall and Agile Methodologies Questions / Comments

Context IowAccess Mission Project Evaluation and Funding Model

Key Attributes - Waterfall Fewer iterations, more features Working Code as the Final Artifact Predictable Scope, Schedule, Cost Emphasis on Formal Steps, Documentation Analysis Design Implementation Testing F1F2F3F4 Scope = Features to Implement

Key Attributes - Agile Many, smaller iterations Working Code as the Primary Artifact Optional Scope Contract, Few Pre-set Goals Emphasis on Individual Commitment Analysis Design Implementation Testing F1 F2F3F4 One Iteration ≈ One Feature F1

Questions, Discussion?

Bibliography / Sources Beck, K., & Andres, C. (2001). Extreme Programming Explained. New York: Addison-Wesley Professional. Melonfire, C. (2006, Sept 22). Understanding the pros and cons of the Waterfall Model of software development. Retrieved June 27, 2009, from Tech Republic: html?part=rss&tag=feed&subj=tr# html?part=rss&tag=feed&subj=tr# Mochal, T. (2003, March 26). Web dev: Pick up speed through standardization. Retrieved June 30, 2009, from Tech Republic: Dubakov, M. (2008, Sept 19). Waterfall got you down with "multitasking"?. Retrieved July 5, 2009 from Edge of Chaos Blog: with.html with.html