Agile software development
Agile software development
Agile software development is a set of principles and practices for software development that emphasizes iterative progress, collaboration, and flexibility. It emerged in the late 1990s as a reaction to the limitations of traditional plan-driven methodologies like the Waterfall model. The core values and principles were formalized in 2001 with the publication of the Agile Manifesto, authored by a group of 17 independent-minded software practitioners.
History
The roots of Agile can be traced to lightweight methods such as Extreme Programming (XP), Scrum, and Dynamic Systems Development Method (DSDM). The term "Agile" itself was coined in 2001 at a ski resort in Snowbird, Utah, where 17 thought leaders gathered to find common ground among these approaches. They produced the Agile Manifesto, which consists of four values and twelve principles. The manifesto prioritizes individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
Key principles
- Deliver working software frequently, with a preference for shorter timescales (e.g., every two weeks).
- Welcome changing requirements, even late in development.
- Business people and developers work together daily throughout the project.
- Build projects around motivated individuals; give them the environment and support they need.
- The most efficient and effective method of conveying information is face-to-face conversation.
- Working software is the primary measure of progress.
- At regular intervals, the team reflects on how to become more effective and adjusts its behavior accordingly.
Common Agile methods
- Scrum – an iterative framework using fixed-length "sprints", daily stand‑up meetings, and roles such as Product Owner and Scrum Master.
- Extreme Programming – practices include pair programming, test-driven development, continuous integration, and frequent releases.
- Kanban – a visual workflow management method that limits work in progress.
- Crystal – a family of methodologies that vary based on team size and criticality.
- Lean software development – derived from lean manufacturing, focusing on eliminating waste and amplifying learning.
Benefits and criticisms
Proponents argue that Agile methods improve adaptability, reduce project risk, and increase team morale. Critics note that Agile can be challenging in large-scale projects, may lack sufficient upfront design, and requires a high degree of customer involvement. The approach has also been criticized for being misapplied as a set of superficial practices without adherence to underlying principles (often called "agile in name only").