1. Overview
The Agile methodology is a set of principles for software development that prioritise flexibility, customer collaboration, and quick delivery over rigid planning and documentation.
2. Origins of Agile
Before Agile, software was typically developed using the Waterfall model – a linear, sequential process.
Problems arose: requirements changed mid-project, documentation-heavy processes slowed delivery, and customers often got what they asked for but not what they needed.
3. Precursors to Agile
Several lightweight, iterative methods emerged to address Waterfall's weaknesses:
Rapid Application Development (RAD)
Scrum (developed in the 1990s)
Extreme Programming (XP)
Feature-Driven Development (FDD)
These shared similar values: shorter cycles, user involvement, and adaptability.
4. The Agile Manifesto (2001)
Seventeen software developers met in Utah and created the Agile Manifesto, which formalised Agile principles.
It valued:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a fixed plan
5. Post-Manifesto Evolution
Agile grew into various frameworks like Scrum, Kanban, Lean, and SAFe.
Widely adopted across industries, not just in software.
6. Conclusion
Agile emerged as a reaction to rigid methodologies. Its success lies in delivering usable software faster while adapting to change and maintaining close collaboration with users.
Glossary
Waterfall Model – a step-by-step, linear approach to software development.
Iterative – a cyclical process where feedback and adjustments happen continuously.
Agile Manifesto – a declaration of the core values and principles guiding Agile.
Scrum/XP/FDD – specific Agile frameworks or methodologies.
Source:
GeeksforGeeks: A Brief History of Agile






0 comments:
Post a Comment
Keep it clean, keep it lean