Business analysis glossary
Agile Manifesto
What it is
The Agile Manifesto is a short statement written in 2001 by a group of software practitioners. It values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. It is supported by twelve principles.
Why it matters
Most agile methods, including Scrum and Kanban, trace their ideas back to the manifesto. Understanding it helps analysts explain why agile teams prefer conversations and small releases, and it corrects a common myth: the manifesto values documentation less than working software, but it does not say documentation is worthless.
Example
In an interview at Skylark Software, Rohan is asked whether analysts are needed in agile teams. He refers to the manifesto: collaboration with customers and responding to change are core values, and analysts make those conversations productive. He adds that he writes just enough documentation for the team to build and test.