Agile Methodology
Definition
Agile Methodology
Agile methodology is an approach to software development that delivers work in short cycles, takes feedback from each one, and changes the plan accordingly. It is a set of values before it is a process, which is why implementations differ so widely.

The founding document is remarkably short. The Manifesto for Agile Software Development, signed by seventeen people in 2001, states four preferences — among them working software over comprehensive documentation — and nothing resembling a method.
Twelve supporting principles sit behind those four lines, and they are more specific than the slogans suggest. One asks teams to deliver working software frequently, naming a couple of weeks to a couple of months as the range, with a stated preference for the shorter.
Governments now audit against it. The US Government Accountability Office published a guide in September 2020 setting out best practices for Agile adoption in federal programs, work it ties to federal IT spending above $90 billion a year.
Key takeaways
- Agile delivers in short cycles and lets real feedback change what gets built next.
- The 2001 Manifesto sets out four values and twelve principles, not a process.
- Scrum, Kanban and SAFe are frameworks that implement agile; none of them is agile itself.
- Most stalled adoptions change team practice and leave funding and governance untouched.
How it works
Agile replaces one long planning bet with many short ones. A team builds a small slice, shows it to somebody who will actually use it, learns something, and allows that learning to change what comes next.
The four values are stated as preferences rather than rules, which is the part most summaries lose.
| Agile values | over |
|---|---|
| Individuals and interactions | processes and tools |
| Working software | comprehensive documentation |
| Customer collaboration | contract negotiation |
| Responding to change | following a plan |
The Manifesto is careful here. It says there is value in the items on the right, and simply values the items on the left more, a hedge that disappears from most corporate retellings.
Frameworks turn the values into mechanics. Scrum is the most widely used of them, giving the cycle a fixed length and a set of events that force inspection at known points.
One of those events is sprint planning, where the team decides what the coming cycle will deliver. The decision belongs to the team, which is the principle doing visible work.
Scale changes the problem rather than the values. An agile release train coordinates several teams on one cadence, while agile portfolio management moves funding from projects to durable teams.
That funding change is where most programmes stop. An agile transformation is an organisation-wide change in how work is governed, and leaving the budget cycle untouched means the teams iterate inside an annual plan nobody will revisit.
Short cycles are not the point in themselves. A short cycle forces a decision to be revisited while changing it is still cheap, and that only holds if somebody actually examines the result.
This is why the feedback step is the one that quietly disappears. Teams keep the cadence, drop the inspection, and end up running waterfall in two-week instalments.

Fixed-price contracts sit awkwardly with all of it. A contract specifying full scope in advance removes exactly the flexibility the method depends on, which is why experienced buyers contract for capacity instead.
Examples
Agile looks different depending on what is being built and who is paying, so the label alone tells you very little. The four cases below are common shapes rather than exemplars, and two of them are only partly agile.
A consumer app team ships every fortnight and watches usage data decide the next feature. This is the textbook case, and it works because releasing is cheap and feedback arrives within days.
A bank modernising a payments platform runs two-week cycles inside an annual budget. The teams are agile, the funding is not, and the mismatch surfaces every time a cycle suggests changing direction.
The team learns quickly and then waits nine months for permission to act on what it learned. Nobody calls that a methodology failure, though that is what it is.
An offshore engineering team in Manila runs the same ceremonies as its client in Sydney, two hours ahead. Software development outsourcing makes the overlap window the real design constraint, not the methodology.
Four hours of shared working time is enough for a daily conversation, and two is not, whatever the process documentation claims. Time zones decide more agile outcomes than frameworks do.
A government department adopts agile under the GAO guidance published in 2020. Progress is measured in working software delivered, which is a materially harder test than milestones completed.
A milestone can be declared complete. Working software either runs or it does not, and that asymmetry is the whole reason the measure was chosen.
Related terms
Agile vocabulary stacks values, frameworks, events and organisational change into one word, and the result is that two people can use it to mean quite different things. Each entry below occupies one of those levels.
- Scrum: the most widely used framework for putting agile into practice.
- Sprint Planning: the event that decides what a team will build in the coming cycle.
- Agile Transformation: an organisation-wide change in how work is funded and governed.
- Agile Release Train: several agile teams planning and releasing on one shared cadence.
- Agile Portfolio Management: funding allocated to durable value streams rather than to projects.
- Software Development Outsourcing: contracted engineering capacity, usually run on agile cadences.
FAQ
Is agile a methodology or a mindset?
Strictly it is neither. The Manifesto sets out values and principles, and the methodologies people mean by the word — Scrum, Kanban, XP — are frameworks built on top of them.
Is agile only for software?
It began there and the Manifesto says software throughout. The practices travel reasonably well to other kinds of knowledge work, though the feedback loop is rarely as fast or as cheap.
Does agile mean no documentation or no planning?
No, and the Manifesto explicitly says otherwise. It values working software more highly than comprehensive documentation, which is a ranking rather than a prohibition.
Why do so many agile adoptions fail?
Because they change how teams work and leave funding, governance and reporting exactly as they were. Teams then iterate inside an annual plan that nobody is willing to reopen.
How is agile different from waterfall?
Waterfall fixes scope up front and discovers problems at the end, while agile fixes time and discovers problems continuously. The difference is mainly when you find out, not how much you plan.
Can an offshore team run agile properly?
Yes, provided the time zones overlap enough for daily contact and the team holds real decision rights. Find engineering partners running agile delivery on Outsource Accelerator.







Independent




