The Challenge to Survive in Today

1
The Challenge to Survive in Todays Software
Development Environment

• Evaluating the Agile Methodology

2
Thesis Hypothesis

• The agile methodologies are better than the
  current methodology that is in place at a company
  that will be used for analysis purposes. This
  companys current methodology is similar to
  Waterfall.

3
Why the need for software development processes?

• Build quality software
• On time
• On budget
• Meets the customers 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

• Idea to improve system functionality, increase
  the business bottom line, or make individuals
  more productive
• Business requirement is written by customer

7
Justify

• Assess the risks and benefits of proposed idea
• Ballpark estimate

8
Review and Approve

• Approve or reject request
• Prioritize approved request

9
Develop A Solution

• Develop Functional Specification
• Develop Detailed Specification
• Reestimate time to develop
• Code and unit test
• Code inspection
• Risk analysis spreadsheet
• QA begins test cases
• Documentation is started

10
Quality Assurance

• Test cases are exercised
• Regression testing is performed
• Developer is available for code rework

11
Implementation

• Software delivery
• User training
• Documentation is given to user
• User acceptance testing
• Sign off on deliverable

12
History of Agile

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

13
Agile Processes

• Extreme Programming (XP)
• Coads Feature Driven Development
• Highsmiths Adaptive Software Development
• Cockburns Crystal Family
• Open Source
• Scrum

14
Why Agile?

• Light weight
• People focus
• Adaptive
• Less Documentation Intensive
• 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

• The agile methodologies are better than the
  current methodology that is in place at a company
  that will be used for analysis purposes. This
  companys current methodology is similar to
  Waterfall.

18
Goal Of Thesis

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

19
Sources