The Agile Manifesto has 4 principles. In Agile 2008, Uncle Bob Martin in his keynote suggested a 5th principle:
Craftsmanship over Execution
(Yes, I’m 3 years late for the party, but bear with me. This came to me as I’m preparing to my NDC talk).
All principles were written by technical people who emphasized communication and value for the customer. The fifth is different. It’s intended for a subset of the group the rest of the principles aim for. Craftsmanship is for the coders.
Makes sense, doesn’t it? But wait…
I’ve been talking about how developers and business people don’t speak the same language. Miscommunication begets mistrust.
By declaring we’re the craftsmen (read: and you’re not!), we’re widening the gap that we’re supposed to bridge together for the customer. And by separating ourselves apart from the rest of the agile team, once again we’re not considered team players.
And there’s less trust.
Ok, now it’s your turn – tell me I’m wrong.
3 comments on “What The 5th Agile Principle Really Means”