Some text within the Manifesto (and Principles) below has been slightly modified to suit business agility overall as opposed to software development teams. Please view the original Manifesto (and Principles) for Agile Software Development here.
Manifesto for Agile Outcomes
We are uncovering better ways of creating outcomes by doing it and helping other do it.
Through this work we have come to value:
Individuals and Interactions
over processes and tools
over comprehensive documentation
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.
Principles behind the Agile Manifesto
We follow these principles:
Our highest priority is to satisfy the customer through
early and continuous delivery of valuable outcomes.
Welcome changing requirements, even late in
creation. Agile processes harness change for the
customer's competitive advantage.
Deliver working outcomes frequently, from a couple of
weeks to a couple of months, with a preference to the
Business people and creators must work together
daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a creation
team is face-to-face conversation.
A working outcome is the primary measure of progress.
Agile processes promote sustainable creation.
The sponsors, creators, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity--the art of maximising the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organising teams.
At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts its