Contents
Agile Model
The Agile model lets teams build and release software changes in small batches, on a regular basis. Planning and analysis are kept lighter compared to traditional models, just enough to know what needs to change. Once the scope is set, the team repeatedly cycles through analysis, design, development, and testing, releasing small updates into production frequently.
Agile Principles and the Agile Manifesto
Agile is based on a set of values laid out in the Agile Manifesto, which prioritizes working software, collaboration with customers, and responding to change over rigidly following a fixed plan. The focus is on flexibility and continuous improvement rather than locking everything down upfront.
Sprints, Iterations, and Increments
Agile teams work in short cycles called sprints, usually lasting one to four weeks. At the end of each sprint, the team delivers a small working increment of the software. Over time, these increments add up to the full product, with regular feedback shaping each new sprint
Agile vs Waterfall
Waterfall | Agile |
| Plans the entire project upfront before development begins. | Assumes requirements can change throughout the project. |
| Follows a strict, sequential process with little room for changes. | Uses short development cycles with continuous feedback and improvements. |
| Best suited for projects with stable and well-defined requirements. | Best suited for projects where requirements are expected to evolve. |










