Is fogbugz amenable to managing work that have nothing to do with software development?
We're a specialized IT shop (Geographic Information Systems) that do a combination of user-focussed support, somewhat analogous to a support help line, and corporate backbone projects: grab whack of data from provider A, convert, model and mash together with provider B's warehouse and serve up to users in nice clean package.
From a thousand feet away, the work we do is similar to software developement. There are milestones and release dates; rarely is something complete, there's just another iteration/version; it's a team effort, some specialize but there's a lot more overlap and sharing of tasks than between, say, plumbers and electricians.
We've looked at a number of "project management" packages (Clarizen, Replicon, AtTask), but they're usually way over engineered and one needs to take a week long course just to figure where to start and how match the pieces together. Their idea of what a "project" is also doesn't mate cleanly with what we do, long and open-ended continuous development. I think they're built around something like engineering a bridge, building an office building or running a bank.
I like fogbugz's user centric approached to data entry, the hundred little things that add up to a near frictionless use. It's like sliding on teflon compared to the apps I've tried. My co-workers shy away at mention of it though, and maybe they're right. What do you think?
