Freshen up Manifesto for Agile Software Development

Posted on

When introducing the Manifesto to new Agile practitioners, its outdated language often got in the way of conversations around more interesting points. So I’ve freshened it up taking inspiration from Kent Beck (talk ‘Beyond Agile Programming’ at Startup Lessons Learned Conference, 2010), Dan North (talk ‘Agile Revisited’ at GOTO conference, 2015) and Joseph Pelrine (ebook on Agile teams and self-organising systems, 2011).

Manifesto for Agile Digital Products development

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 processes and tools
Working features & validated learning over comprehensive upfront documentation
Customer collaboration & discovery over contract negotiation
Initiating & 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 behind the Agile Manifesto

We follow these principles:

Our highest priority is to delight the users and the customer
through early and continuous delivery of business value.

We welcome emerging requirements, even late in development.
Agile processes harness change
for the customer’s competitive advantage.

Deliver business value and working features, and validate learnings
continually, from a couple of weeks to a couple of hours,
with a preference to the shorter timescale.

Business and product people, developers and designers, and everyone else
must work together daily throughout the delivery effort,
end-to-end from concept to cash.

Build digital 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 development
team is face-to-face conversation.

Working features, delighted customers and business value
are the primary measures of progress.

Agile ways of working 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
enhances agility.

Simplicity –the art of maximising the amount
of work not done– is essential.

The best products, architectures, requirements, and designs
emerge from a team part of a self-organising system
that supports and amplifies beneficial outcomes.

Continuously the team reflects on how
to become more effective, then tunes and adjusts
its behaviour and ways of working accordingly.