Antimatter Principle Elaborated

Around a year ago I wrote a post with the title “Antimatter Evo“. For those who may have found it a little over-long, and for those who prefer lists, I’ve extracted the core Antimatter Principle elements into this briefer post ( corresponding, BTW, to the twelve principles of the Agile Manifesto). And I’ve also added a list of related Think Different posts under “Further Reading”.

Twelve Principles for Software Development

The Twelve Principles of Agile Development as seen through the Antimatter Principle lens, and its vocabulary:

1. Our only priority is to continually attend to the needs of everyone that matters.

2. Handle changing needs, and changing membership of the “everyone that matters” community, in ways that meet the needs of the folks that matter.

3. Deliver stuff as often as, and by means that, meets the needs of everyone that matters.

4. Share needs and solutions as often as, and by means that, meets the needs of everyone that matters.

5. Motivate people to the degree that, and by means that, meets the needs of everyone that matters.

6. Facilitate sharing of information, feelings, needs, etc. to the degree that, and by means that, meets the needs of everyone that matters.

7. Choose a primary measure of progress that meets the needs of everyone that matters.

8. Choose a pace that meets the needs of everyone that matters.

9. Agree on attributes of quality, and levels of quality, with respect to the means of the endeavour, that meets the needs of everyone that matters.

10. Spend effort only where it directly attends to some need of someone that matters.

11. Agree on attributes of quality, and levels of quality, with respect to the organisation of the endeavour, that meets the needs of everyone that matters.