The new business-friendly version of the original Agile Manifesto: The Lean-Agile Manifesto for Digital Products and Services. Inspired by Kent Beck (talk ‘Beyond Agile Programming’ at Startup Lessons Learned Conference, 2010) and by Dan North (talk ‘Agile Revisited’ at GOTO conference, 2015).
Business friendly Lean-Agile Manifesto for Digital Products and Services
We are uncovering better ways of developing
digital products by doing it and helping others do it.
Through this work we have come to value:
Team vision and discipline over individuals and interactions over processes and tools
Validated learning over working software over comprehensive documentation
Customer discovery over customer collaboration over contract negotiation
Initiating change over 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.
Twelve Principles of Lean-Agile Digital Products/Services
We follow these principles:
Our highest priority is to satisfy the customer
through early and continuous delivery of value.
Welcome emerging requirements, even late in development.
Lean-Agile processes harness change
for the customer’s competitive advantage.
Deliver working software continually,
from a couple of weeks to a couple of hours,
with a preference to the shorter timescale.
Business people and developers and everyone else must work
together daily throughout the project.
Build products 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 business, product, and development
team is face-to-face conversation.
Business impact is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, users, and all stakeholders
should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design
Simplicity–the art of maximising the amount
of work not done–is essential.
The best architectures, requirements, and designs
emerge from teams in an environment that supports
and amplifies positive outcomes from self-organisation.
Continually, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.