• It's all so very "big company".

    In a smaller outfit like this with only half a dozen in the dev team covering DBA, design, development and day-to-day application support, you have to work with the business users who have to test and accept any software before it goes out. The ITIL framework is the basis for things, but we don't give it any fancy names, we just do it.

    Couldn't agree more!

    I've almost always worked as a dev at small companys (nb. not "start ups") and I've always been happy stepping into all the roles from DBA, business anallyst, project manager etc. In fact I'm not just comfortable with it, I actively enjoy it. I don't fool myself that that I'm an expert in all those fields but I'm happy that I'm good enough to get the job done satisfactorily 99% of the time. For the other 1% I'll turn to the expert.

    And while there are some roles (DBA's an obvious one) that can be comfortably pushed off into a silo without too much risk there are many (and I think the various analyst roles fall firmly in this bracket) that are much better done by the same individual who'll do the development because of the amount of crucial information that get's lost in communication. The thought of not being able to communicate directly with my end users fills me with dread.

    Lord save us from devs (or anyone else) who want to sit in ivory towers.

    edit>Also, as a Dev can I just say how heartily I endorse Jeff Knupps hierarchy of usefulness.;-)