I know most IT departments vary greatly depending on size and type of company, but I'm just wondering what the typically IT org chart would look like.
closed as primarily opinion-based by HopelessN00b Jan 21 '15 at 15:49
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
locked by HopelessN00b Jan 21 '15 at 15:50
This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.
Read more about locked posts here.
In small and medium businesses (SME) IT departments have historically grown organically, and often haphazardly.
In large organizations, they have come to mimic typical organizational structure for a department or division, often if not a core business function (i.e. you don't sell IT services) it is viewed as a non-revenue generating expense (like legal, HR, and too often like facilities management).
You'll see a CIO or VP of (Information) Technology at the top, with managers for each divisions.
Common division titles: Operations, Development, Networking (Infrastructure), Information Management / Data warehousing / Database Group, and Client Services or Help-desk. These divisions are not uniform in naming, but often their basic or core function is identical regardless of the naming (Development is sometimes simply called Software for example).
I think ITIL and PRINCE2 might be two sources that could have more "standard" terms or org charts. I cannot think of any other practices or methodology, but anything that is an "expensive buy in, and main purposes seems to exist solely to be the basis to justify yet another re-organization" would be suitable. While this sounds (and is) cynical, I believe most of it is reasonably accurate to be suitable sources for potential answers.
I started drawing a chart to show our IT department but as there is only one of me it just ended up looking like a circle.
Kyle nailed it in that comment up there. More seriously, there isn't much in the way of 'typical'. There are many, many ways to arbitrarily draw lines between IT functions. Generally speaking, the larger the organization the more specialized IT functions can get. General Motors can afford Storage Architects and entire departments of people devoted to supporting a single (very important) application. The local community college may have three people who do it all, with a few professor-types assisting. Your local City may have IT as a sub-unit of the Finance Office, even though Public Works is one of the biggest consumers of data (all that sub-street information to keep track of).
Mmmyeah. Talking about a typical IT department is about as easy as talking about your typical mammal.
It depends on how you isolate the different roles: networking, systems, applications, qa, etc.. Oh yeah, don't forget your CIO, if you have one. In our case, we're under the Finance umbrella.
Support and Code monkeys at the bottom
Failed code monkeys higher up in the food chain... analysts, project managers, line managers etc
I'm quite serious: developers are mainly happy being developers and don't see BA/PM/LM as a career progression...
I'm in the IT division of a large global company.