Introduction
Agile is a set of values and principles for software development that prioritises people, collaboration, and the ability to respond to change over rigid plans and heavyweight processes. It is not a single methodology — it is a mindset from which frameworks like Scrum, XP, and Kanban emerge.
The movement was formalised in February 2001, when seventeen software practitioners met in Snowbird, Utah, and published the Manifesto for Agile Software Development. The manifesto is deliberately short — four values and twelve principles — because the authors believed that prescriptive processes were part of the problem, not the solution.
The Four Values
The manifesto states:
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
These are not binary choices. The manifesto explicitly acknowledges that processes, documentation, contracts, and plans have value — but when forced to choose, agile teams lean towards the items on the left.
The Twelve Principles
Behind the values sit twelve principles that guide how agile teams operate in practice. A few worth highlighting for technology leaders:
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
- The best architectures, requirements, and designs emerge from self-organising teams.
- Working software is the primary measure of progress.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The full set of twelve principles is available on the Agile Manifesto website.
Why CTOs Should Care
Agile is the dominant delivery paradigm in modern software organisations, but its real value is often diluted by cargo-cult adoption — teams that follow ceremonies without internalising the underlying values. As a technology leader, your job is to ensure agile is applied as a thinking tool, not a compliance checklist.
- Faster feedback loops: Short iterations surface problems early, reducing the cost of change and the risk of building the wrong thing.
- Team autonomy and ownership: The manifesto's emphasis on self-organising teams maps directly to high-performing engineering cultures where teams own outcomes, not just outputs.
- Adaptability over prediction: In uncertain markets, the ability to pivot quickly is more valuable than a detailed five-year roadmap.
- Quality as a default: Practices like TDD, continuous integration, and frequent releases — all rooted in agile principles — build quality in rather than inspecting it out.
The methodologies in this section — from Scrum and XP to Kaizen and retrospectives — are all practical implementations of these foundational values. Understanding the manifesto helps you evaluate which practices actually serve your teams and which are just process theatre.
Explore Next
- Scrum — A lightweight framework for iterative, incremental delivery in small cross-functional teams.
- Extreme Programming (XP) — Engineering-driven practices like TDD, pair programming, and continuous integration.
- SAFe — The Scaled Agile Framework for coordinating agile across large organisations.
- Kaizen — The philosophy of continuous, incremental improvement.
References
- Manifesto for Agile Software Development — The original 2001 manifesto that defined the four values and twelve principles of agile.
- Principles behind the Agile Manifesto — The twelve supporting principles that underpin the Agile Manifesto.
- History: The Agile Manifesto — Background on how seventeen software practitioners came together to write the manifesto.