Iterative/Agile for the (Non-Software-Developer) Hobbyist?
So, I just got back from Anime Weekend Atlanta. It was a fun time, and I swear there's a blog post coming... right after I finish my long-overdue post for DragonCon.
My friends and I attended a couple of the costuming panels, mainly armor making and steampunk. And there seems to be some traction of trying to do a steampunk group for next year, which I'm all for--I like the idea of getting everyone together to work on a project as a group, although I'm not quite as gung-ho about steampunk as some of them.
The problem is, discussion evolved from creating some basic themed costumes into talk of complex armor and props as the centerpiece. It went from things we know how to do (sewing and simple props) to things we don't (woodworking or vacu-forming or resin-casting or even large-scale paper maché).
In a word: feature creep. Waterfall design. One that could easily end up half finished before it runs out of... um, steam. No question that it's creative outside-the-box thinking. But you need to think inside-the-box to wrangle that vision into something possible and affordable.
As a software developer, I'm naturally inclined to think iteratively. Start with the essential stuff that you know you can do. If you go no further, at least you have something usable. Then, when you have a working product, start tackling the tough stuff that you've not as familiar with. Break it up into phases, and be willing to say "I'm done" at the end of any phase if time, money, or motivation force you to do so.
Now, when you're talking about projects in the real world, you can't always do that. It's tough to construct a single building in stages. Nor can you call a painting done once you've done the preliminary outlining. Nor would formal agile methodologies work quite the same way in a casual, small group environment. But it seems there's some value in having this alternate perspective in the back of your mind to guide you as you do your planning.
It makes me want to write an article series, a con panel, something that would introduce these concepts in non-technical language to people outside of software development. Not to spread the agile kool-aid around (because if there's one thing I hate, it's buzzword kool-aid), but to give hobbyists of various types another tool in their toolbox that they can use when it's appropriate.
Surely someone out there's already written this, though. Anyone know where to find it?
Post a Comment
To post a comment to this blog entry, login below: