Do we really need a manifesto for software craftsmanship?

This seems like a reaction to, maybe an extension of, the Agile Manifesto. I don’t see anything that I object to, but maybe that’s just because I (and the teams I lead who adopted and signed the Agile Manifesto) believed those “implementation details” were already covered.

  • Not only working software, but also well-crafted software
  • Not only responding to change, but also steadily adding value
  • Not only individuals and interactions, but also a community of professionals
  • Not only customer collaboration, but also productive partnerships

Manifesto for Software Craftsmanship

Can’t hurt, I guess, since some people need to have every little detail spelled out for them.

Comparing the state of the art of software development to where it was before the “agile revolution”, I think we’ve come a long, long way!!

Skip to main content