For those of you who are computer geeks (don’t worry, I won’t give it away), I’ve got a new piece “Less Process, More Discipline” up at Software Quality Connection.
Haven’t read it, like the title…
OK, read it.
Precisely right — agile works iff you follow the disciplines. The problem is, they’re hard, and it’s easier to have meetings.
The fight I’m caught in right now is the discipline of choosing technologies that support the rest of the disciplines. “Yeah, that’s neat — but how do you test that?”
I think (having been a tool geek for a fairly long time) that tools and technologies are to some extent a trap. You’re better off with index cards until you really have some idea what the limits are.
No, not those technologies. Development technologies; libraries.
The particular case is a UI toolkit that is actively hostile towards testing. I had an application where unit and integration testing had over 90% code coverage, then other developers brought in the “latest and greatest” — and coverage has since slipped to a hair under 50% as new code (mostly around the UI) cannot be tested.
It’s not the biggest reason the project’s in trouble, but it still grates on my nerves every time I think about it.
Well, I something think GUIs are a trap too, but that’s just ’cause
– Hey! You kids! Get the hell offa my lawn!
Great article, Charlie.
Your final point applies to every agile endeavor: “The key to agile methods is this: You may have less process, but you must have more discipline.”
Well done CM.
This applies beyond the world of SW development. Process and methods should provide a framework to organize your hard work. Too many people treat them as a substitute for hard work, including the hard work of knowing what you want to do in the first place.
Rob is right – they’re hard, and it’s easier to have meetings.
Comments are closed.
Copyright © 2005-2012 PJ Media All Rights Reserved. v1.000020