Agile
What is Agile?
Agile is a way of working in which a team ships small, usable pieces often, collects feedback and changes its plan as it learns. The name was set by the 2001 Agile Manifesto, which grouped methods such as Scrum and XP.
Updated November 2026 · 3 min read
Agile is an approach to building products and running projects in which a team delivers work in small, usable increments, gets feedback early and often, and adjusts its plan based on what it learns. Instead of defining everything up front and delivering once at the end, an agile team plans in short cycles, ships something working each cycle and treats change as normal rather than as a failure of planning.
The term comes from software. In February 2001, seventeen practitioners met in Snowbird, Utah, and wrote the Manifesto for Agile Software Development, which set out four values and twelve principles. Several of the methods they represented, including Scrum, Extreme Programming (XP), DSDM and Crystal, already existed; "agile" became the shared name for them. The ideas have since spread to marketing, operations, HR and portfolio management.
Core ideas behind Agile
- Iterative and incremental delivery. Work is broken into small pieces that are built, tested and delivered in short cycles, usually one to four weeks.
- Fast feedback. Customers and stakeholders see working results often, so misunderstandings surface in weeks, not months.
- Empirical planning. Plans are updated from evidence, such as what the team actually completed and what users actually did.
- Cross-functional, self-managing teams. One team holds the skills to take an item from idea to done and decides how to do the work.
- Continuous improvement. Teams regularly reflect on how they work and change it.
Agile frameworks and methods
| Method | Main idea | Typical use |
|---|---|---|
| Scrum | Fixed-length sprints, three accountabilities (Product Owner, Scrum Master, Developers) and a set of events | Product teams building new features |
| Kanban | Visualize work, limit work in progress and manage flow continuously | Support, operations and teams with unpredictable demand |
| Extreme Programming (XP) | Engineering practices such as pair programming, test-driven development and continuous integration | Software teams that want high technical quality |
| Scrumban | Scrum's planning rhythm combined with Kanban's flow controls | Teams moving between the two |
| SAFe, LeSS and others | Coordinating many agile teams on one product or portfolio | Large organizations |
Agile vs. waterfall
In a waterfall project, requirements, design, build, test and release happen in sequence, and the customer usually sees the result near the end. That works when requirements are stable and well understood. Agile suits work where requirements are uncertain or likely to change, because it lets the team learn and correct course every cycle. Many organizations use a mix: fixed regulatory milestones planned up front, with agile delivery inside them. See agile vs. waterfall for a fuller comparison.
Agile in practice: A worked example
Consider a hypothetical team asked to build a customer self-service portal. A waterfall plan estimates nine months: three of requirements and design, four of development and two of testing, with the first user feedback in month nine.
The agile version starts with a two-week sprint that delivers one capability, letting customers download invoices, to a pilot group of 50 customers. Feedback in sprint two shows that customers care far more about updating payment details than downloading invoices, so the team reorders the backlog. By the end of month three, after six sprints, the portal covers the three tasks behind most billing support tickets and is open to all customers. Several features in the original specification are dropped because usage data shows nobody needs them. The first customers get value in week two, and the full portal is live six months before the waterfall plan would have delivered it.
Benefits and limits
Agile tends to reduce the risk of building the wrong thing, makes progress visible and lets organizations respond to change. Its limits are real too. It needs an engaged product owner and stakeholders who will review work frequently. Fixed-price, fixed-scope contracts sit awkwardly with it. And scaling it across many teams brings coordination costs that frameworks only partly solve.
Common pitfalls
- Adopting the ceremonies without the intent. Daily standups and sprints with no working increment and no real feedback are waterfall with extra meetings.
- Treating agile as "no planning." Agile teams plan constantly, just in smaller, more frequent steps.
- Measuring velocity as productivity. Story points are a team's planning tool, not a performance score to compare teams.
- Leaving management unchanged. If budgets, approvals and reporting still assume fixed annual plans, teams cannot act on what they learn.
- Skipping technical practices. Without automated testing and continuous integration, frequent delivery becomes frequent breakage.
Agile connects to the agile principles and agile mindset, and at organizational scale to agile transformation and agile portfolio management.
Frequently asked questions
When is agile not the right approach for a project?
Agile adds the most value when requirements are uncertain or likely to change. When requirements are stable and well understood, a sequential waterfall plan can work well. Agile also struggles without an engaged product owner and stakeholders willing to review work often, and fits awkwardly with fixed-price, fixed-scope contracts. Many organizations mix fixed milestones with agile delivery inside them.
Which agile framework should a team choose?
It depends on the work. Scrum suits product teams building new features in fixed-length sprints. Kanban suits support, operations and teams with unpredictable demand. Extreme Programming focuses on engineering practices for high technical quality, and Scrumban blends Scrum's rhythm with Kanban's flow controls. Large organizations coordinating many teams often add SAFe, LeSS or a similar scaling framework.
Is velocity a good measure of agile team productivity?
No. Velocity, usually counted in story points, is a team's own planning tool and should not be used as a performance score or to compare teams. Treating it as a target tends to inflate estimates rather than output. Agile progress is better judged by working increments, customer feedback and whether the outcomes the work was meant to change actually moved.
Related terms
Agile Manifesto
The 2001 founding statement of agile's four values and twelve principles.
Scrum
An agile framework of short Sprints, three roles and regular inspection.
Kanban
Visualizing work, limiting work in progress and improving the flow.
Scrumban
A blend of Scrum ceremonies with Kanban's board, WIP limits and flow.