When I was at school we got a new headmaster. My parents weren’t overly impressed; he came with a wave of new educational ideas that they disliked. He did, however, say one thing that stuck with me. At one particular assembly he affirmed that the school only had one rule: “use common sense” in everything that we did and said.
This stuck with me firstly because of the misnomer that he then went on to site rules that the school clearly had, which he insisted didn’t exist. And secondly because he was right; common sense does seem to be a good approach to most things.
Which brings me to agile. Or more specifically “agile, but” or “agile, and”. Or the variances to agile under the “but” or “and” banners. Which I just don’t get.
First, agile has a clear set of values and principals all of which leave plenty of room for maneuver. There are no “do this, don’t do that” rules.
Second, if I’m to be but this or and that, then I’d better know where I’m starting from. I’ve read a range of books and whilst in the absolute detail they may marginally differ, I’m not committed to any particular one. I’m committed to agile.
Third, if I go for one or other, then I need to write the rules that I’m applying; that’s never going to happen (…over comprehensive documentation!)
And forth, we employ, and I like to think I only work with intelligent people. They should use their initiative (individuals and interactions over process and tools) not be driven by a check list of activity.
So I’m for Agile, not “but”, not “and”, just because…because its better!
Thanks for the image