Agile Methodology

Definition

Agile is not a single method, but a mindset and a collection of principles and practices. The core ideas were articulated in the "Manifesto for Agile Software Development" in 2001. The 12 principles behind the manifesto emphasize values like customer collaboration over contract negotiation, and responding to change over following a plan. Agile methodologies (like Scrum, Kanban, and Extreme Programming) provide frameworks for implementing these principles. In an Agile approach, work is broken down into small increments, developed in short iterations (sprints), and continuously delivered and improved based on feedback.

Origin & Context

Agile methods were developed in the 1990s as a reaction to the perceived failures of heavyweight, documentation-driven software development methodologies like the Waterfall model. The 2001 meeting of 17 software developers in Snowbird, Utah, and the resulting Agile Manifesto, formalized the movement.

Why It Matters

In a rapidly changing business environment, the traditional 'big bang' approach to projects is often too slow and too risky. By the time a multi-year project is delivered, the business needs may have changed. Agile provides a way to deliver value to customers faster, get feedback earlier, and adapt to changing requirements. For business architects, understanding Agile is critical for ensuring that architecture is not a bottleneck but an enabler of rapid, iterative delivery. This has led to the emergence of 'Agile Architecture' practices.

Common Misconceptions

Myth: Agile means no planning and no documentation.

Reality: Agile values 'just enough' planning and documentation, done at the 'last responsible moment'. The goal is to avoid the waste of extensive upfront planning that may be invalidated by changing requirements.

Myth: Agile is only for software development.

Reality: Agile principles and practices are now being applied to a wide range of business functions, including marketing, HR, and even strategic planning.

Practical Example

A software team using the Scrum framework works in two-week 'sprints'. At the start of the sprint, they plan the small batch of features they will build from a prioritized 'product backlog'. They have a short 'daily stand-up' meeting to coordinate. At the end of the sprint, they demonstrate the working software to stakeholders ('sprint review') and reflect on their process ('sprint retrospective'). This cycle repeats, allowing them to deliver a new, tested increment of the product every two weeks.

Industry Applications

Any

Agile is now the dominant approach for software development in virtually every industry. Its principles are also being adopted for managing complex projects and transformation initiatives beyond IT.

Related Terms

• DevOps: DevOps extends Agile principles from development to operations, focusing on automating the delivery pipeline to enable continuous deployment.
• Design Thinking: Design Thinking is often used in the 'discovery' phase of an Agile project to define the user needs that will populate the product backlog.
• Product Thinking: The shift to a product-centric operating model is a key enabler for adopting Agile at scale.