1 / 6

Agile Software Development: Collaborative, Iterative, and Customer-focused Approach

Agile software development is a collaborative approach focused on iterative development, self-organizing teams, customer collaboration, and responsiveness to change. This article explores the principles of Agile and its benefits compared to traditional software development methodologies.

felder
Download Presentation

Agile Software Development: Collaborative, Iterative, and Customer-focused Approach

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. Week 10 Agile Software Development Process

  2. What is Agile? • Agile software development: describes a set of values and principles for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams. (Wiki) • Agile is a way of producing software in short iterations on a continuous delivery schedule. Other areas of focus include self-organizing teams, simplicity, sustainable pace of development, and change based on customer feedback. (IBM)

  3. Backlog Plan Plan Plan Build Test Build Test Build Test Iteration 1 Iteration 2 Iteration n Software due date What is Agile?

  4. What is the problem with SDLC? • Traditional software development such as SDLC/Waterfall, normally requires several months for planning and writing specifications, and multiple months for coding and testing the software. By the time you completed the software, it might be months or years behind what you clients were asking for. Change of requirements would prolong the project further. • On the other hand, one of the principles of Agile is response to change of requirements.

  5. The Agile Manifesto • In 2001, a group of seventeen IT professionals (consultants and developers) gathered at Snowbird, Utah. • The outcome of that meeting was “The Agile Manifesto”: • Individuals and interactions over process and tools. • Working software over comprehensive documentation. • Customer collaboration over contract negotiation. • Responding to change over following a plan.

  6. References • http://www.agilemanifesto.org. • https://www.ibm.com/developerworks/rational/library/mar07/pollice/index.html • https://www.ibm.com/cloud/garage/content/culture/practice_agile_principles/

More Related