Today it’s 17.5 years ago the gathering leading up to the Agile Manifesto ended.
It’s a great description on the way you want to develop software:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
I found out that I’ve been trying to that for my whole career – even before I knew about the Agile Manifesto – despite my actual nature being a bit on the autistic side that makes the “human” thing a bit harder for me, but not impossible.
In my day to day work, I try to encourage people to develop in the same way and to also broaden their perspective.
So while writing this, I remembered that doing so (both developing and encouraging) isn’t always easy and requires a lot of craftsmanship. This then reminded me of another manifesto I had seen a while ago, but had forgotten about.
After some digging, I found it back: the “Manifesto for Software Craftsmanship” from 2009 which is subtitled “Raising the bar”
Later I even found back who referred me to it: [WayBack] Great companion to the Agile ManifestoManifesto for Software Craftsmanship – Marjan Venema – Google+
I like it because it defines Craftsmanship as an enhancement of Agile by going a level deeper on all the points of the Agile Manifesto:
-
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
–jeroen
References:
Like this:
Like Loading...