Why not combine the Agile Manifesto and the Software Craftsmanship Manifeso?

Here's my suggestion, trying to remain faithful to the meaning, spirit, and brevity of the originals.

Agile Crafted Software Values

An interacting community of professionals over processes and tools

Well-crafted, working software over comprehensive documentation

Productive collaboration and partnerships over contract negotiation

Responding to change by adding value over following a plan

That is, while there is value in the items on the right, we have found the items on the left to consistently yield greater benefits.


Arguably, the most influential document for modern software engineering is the 2001 Agile Manifesto, laying out the values and principles of what it means to develop in an effective way. It's easy to forget--or even not ever read--these principles, instead believing that they're enforced by the various methodologies. Several original signatories have rightly complained about what's happened to their vision.

Agile has been taken over by corporations to make a buck.

I think it's important to remember two things:

  1. Agile is not a method. Methods should implement agile values and principles.
  2. Agile methods aren't for project management. They're for software development.

Thus, in 2009, Software Craftsmanship was proposed to reaffirm the central role of developers.

These shouldn't exist separately. By combining them, I think value is added.