1 / 15

Agile Software Development

Agile Software Development. Sri Sudhir Naidu CS 532. Traditional Software Development. Less communication between Customers and clients. Requirements process in sealed before Analysis and design process. Take more than estimated time and estimated budget. Agile Modeling. What is agility ?

elan
Download Presentation

Agile Software Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile SoftwareDevelopment Sri Sudhir Naidu CS 532

  2. Traditional Software Development • Less communication between Customers and clients. • Requirements process in sealed before Analysis and design process. • Take more than estimated time and estimated budget.

  3. Agile Modeling • What is agility ? • Where is it needed ? • What are Agile Software Development models? • Why do we choose Agile Software Development ?

  4. What is Agile Modeling (AM)? • A practice-based methodology for effective modeling and documentation of software-based systems. [1]

  5. The Goals of AM: • To put into practice, a collection of values, principles and practices pertaining to effective and light-weight modeling.

  6. The Scope of AM: Figure : AM enhances other software processes.

  7. AM Values: • Communication • Simplicity • Feedback • Courage • Humility.

  8. AM Principles: • Assume Simplicity • Embrace Change • Incremental Change • Rapid Feedback • Model with a purpose and need multiple models • Software is the primary goal.

  9. AM Practices • Active Stakeholder Participation • Apply the Right Artifacts • Consider ownership • Consider Testability • Models in small increments and working parallel

  10. Agile process Philosophy • Individuals and interactions over processes and tools. • Working software over comprehensive documentation • Customer collaboration over contract negotiations. • Responding to change over following a plan.

  11. When is a Model Agile? • If there is a such thing as agile modeling, then there are also agile models. • Agile models are good enough when they exhibit the following criteria: • They fulfill their purpose and no more. • They are understandable. • They are sufficient accurate.

  12. Agile Software Development Methods (Processes) • Incremental Small releases, rapid cycles • Cooperative and communication • Straightforward • Adaptive

  13. Agile Models • XP( Extreme Programming) • Scrum • Feature Driven Development (FDD) • Dynamic Systems Development methods

  14. Conclusion: When go agile? • Uncertain & volatile requirements. • Responsible & motivated developers • Customers who understand and willing to get involved. • AM manage and optimize cost and time of the project.

  15. References • Manifesto for Agile software development; http://agilealliance.com • New methodology; Fowler; Martin; http://www.martinfowler.com/articles/newMethodology.html • Agile software development: Evidence from the field. AlanMacCormackhttp://www.agiledevelopmentconference.com/2003/ files/AlanAgileSoftwareJun03.ppt

More Related