Agile
Agile (agile software development) is an approach to project management in which work is split into short, repeating cycles (iterations) that each deliver a working piece of the product, rather than delivering the whole project in one long phase. Its foundation is the four values and twelve principles of the Agile Manifesto from 2001.
How Agile works
The Agile Manifesto values individuals and interactions over processes, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a rigid plan. In practice this means working in short cycles (for example two weeks), after which the team presents results, gathers feedback, and plans the next step. Requirements are kept in a backlog and prioritized continuously, so the product can evolve with market needs.
Agile is not a single method but a philosophy realized through concrete frameworks. The most popular is Scrum, with its roles, sprints, and ceremonies; alongside it teams use Kanban and Extreme Programming.
Agile in practice
Agile is the standard in development teams where requirements change often and fast delivery of value is crucial. A team building a web application can ship new features in each sprint and test them immediately with users, rather than waiting months for one large release. The agile approach pairs well with DevOps practices and automated deployments in CI/CD pipelines, allowing more frequent and safer releases. It is now applied beyond software too — in marketing and product design — wherever quick testing of hypotheses matters, though calling a process agile does not help without a genuine culture of collaboration.
Powiązane pojęcia
Najczęstsze pytania
Is Agile the same as Scrum?
No. Agile is a broad approach and set of values described in the Agile Manifesto, while Scrum is one specific framework that puts those values into practice. Besides Scrum, you can also work in an agile way with Kanban or XP.
When is Agile a poor fit?
Agile can be less effective in projects with a rigid, fixed scope and strict regulatory requirements where full upfront documentation is essential. In such cases waterfall-style approaches sometimes work better.
