Agile software development emerged in the late 1990s to address the need for rapid development and delivery in a fast-changing business environment. It emphasizes iterative processes, stakeholder involvement, and minimal documentation, focusing on delivering working software quickly. The Agile manifesto prioritizes individuals and interactions, working software, customer collaboration, and responding to change over traditional processes and documentation.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
14 views10 pages
AGILE
Agile software development emerged in the late 1990s to address the need for rapid development and delivery in a fast-changing business environment. It emphasizes iterative processes, stakeholder involvement, and minimal documentation, focusing on delivering working software quickly. The Agile manifesto prioritizes individuals and interactions, working software, customer collaboration, and responding to change over traditional processes and documentation.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10
Agile Software
Development By Attia Agha Topics
✧ Agile methods ✧ Agile development techniques Rapid SE
Rapid development and delivery is now often the most important
requirement for software systems Businesses operate in a fast –changing requirement and it ispractically impossible to produce a set of stable software requirements Software has to evolve quickly to reflect changing business needs. Plan-driven development is essential for some types of system but does not meet these business needs. Agile development methods emerged in the late 1990s whose aim was to radically reduce the delivery time for working software systems Agile development
Program specification, design and implementation are inter-leaved
The system is developed as a series of versions or increments with stakeholders involved in version specification and evaluation Frequent delivery of new versions for evaluation Extensive tool support (e.g. automated testing tools) used to support development. Minimal documentation – focus on working code Plan-driven and agile development Plan-driven development A plan-driven approach to software engineering is based around separate development stages with the outputs to be produced at each of these stages planned in advance. Not necessarily waterfall model – plan-driven, incremental development is possible Iteration occurs within activities. Agile development Specification, design, implementation and testing are inter-leaved and the outputs from the development process are decided through a process of negotiation during the software development process. AGILE METHODS
Dissatisfaction with the overheads involved in software design methods of
the 1980s and 1990s led to the creation of agile methods. These methods: Focus on the code rather than the design Are based on an iterative approach to software development Are intended to deliver working software quickly and evolve this quickly to meet changing requirements. The aim of agile methods is to reduce overheads in the software process (e.g. by limiting documentation) and to be able to respond quickly to changing requirements without excessive rework. Agile manifesto
We are uncovering better ways of developing software by doing it and
helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Principle of agile methods Agile method applicability
Product development where a software company is developing a small or
medium-sized product for sale. Virtually all software products and apps are now developed using an agile approach Custom system development within an organization, where there is a clear commitment from the customer to become involved in the development process and where there are few external rules and regulations that affect the software.