It’s not only about making something work. Just coding the “simplest thing that could possibly work” is not how your final product should look like. That’s not code that should go into production and I believe it shouldn’t bother your continuous integration process either.
It’s not about just killing bugs and being able to change requirements no matter what. It’s about doing it the best way by producing easily maintainable legagy code.
It’s not about getting together everyday for 10 minutes while standing up and calling it “Daily Scrum”, or “Dailly Meeting”. It’s about exchanging ideas and sharing your recently gained experience, as well as learning from others.
It’s not about having someone who you can call “client”. Having a client is just one of the many steps towards agile development (and a very important step). It’s more than that. You need a partnership with someone that seeks business value and is willing to invest in it.
It’s not about getting it done, it’s about doing it right.
This is the Software Craftsmanship Manifesto:
As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:
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.
That is, in pursuit of the items on the left we have found the items on the right to be indispensable.



Muito bom…esse é um reforço para os que se dizem ágil, mas não lembram de coisas que devem estar sempre presentes no desenvolvimento, a qualidade é regra para qualquer metodologia, até mesmo cascata
[...] programa deve simplesmente funcionar. Simplesmente funcionando também não é o que procuramos e o software craftsmanship manifesto esclarece isto muito [...]