1. The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology

2. Thesis Hypothesis b The agile methodologies are better than the current methodology that is in place at a company that will be used for analysis purposes. This company’s current methodology is similar to Waterfall.

3. Why the need for software development processes? b Build quality software b On time b On budget b Meets the customer’s requirements

4. Waterfall Process

5. Waterfall Example 1. Develop an Idea 2. Justify 3. Review and approve 4.Develop a solution 5.Quality Assurance 6. Implementation

6. Develop an Idea b Idea to improve system functionality, increase the business’ bottom line, or make individuals more productive b Business requirement is written by customer

7. Justify b Assess the risks and benefits of proposed idea b Ballpark estimate

8. Review and Approve b Approve or reject request b Prioritize approved request

9. Develop A Solution b Develop Functional Specification b Develop Detailed Specification b Reestimate time to develop b Code and unit test b Code inspection b Risk analysis spreadsheet b QA begins test cases b Documentation is started

10. Quality Assurance b Test cases are exercised b Regression testing is performed b Developer is available for code rework

11. Implementation b Software delivery b User training b Documentation is given to user b User acceptance testing b Sign off on deliverable

12. History of Agile b Several agile processes were developed during the 1990’s b Group of individuals gathered at lodge in February 2001 b Developed Agile Manifesto b Formed Agile Software Development Alliance

13. Agile Processes b Extreme Programming (XP) b Coad’s Feature Driven Development b Highsmith’s Adaptive Software Development b Cockburn’s Crystal Family b Open Source b Scrum

14. Why Agile? b Light weight b People focus b Adaptive b Less Documentation Intensive b Handles changing requirements better

15. Agile Manifesto Values  “Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation.  Responding to change over following a plan.” [Agile Manifesto]

16. Feature Driven

17. Thesis Hypothesis b The agile methodologies are better than the current methodology that is in place at a company that will be used for analysis purposes. This company’s current methodology is similar to Waterfall.

18. Goal Of Thesis b Describe agile processes of Extreme programming, Feature Driven, and Adaptive b Evaluate if the company used as an example should stay with waterfall, reengineer, or change to an agile methodology b Estimated Completion: Fall 2002

19. Sources