Q:

What is the typical IT support team structure and their general areas of knowledge?

The place I work has purchased SharePoint 2010 Enterprise, for many reasons, but firstly for document management.  
However they are keen to get to most out of the 'rest of it'.  But us developers have no previous experience of SharePoint, other than what we are all eagerly trying to learn, using on-line learning materials.  I think it's for a user base of approx 6000.
We are trying to work out some of the skills that a core support team would need and how many people it usually takes.

Is there a typical 'support team' structure? 
If so, what are the core
set of SharePoint skills they need?

A:

There is really no single set of best practices here. The best practice is usually what works best for a given organization. However, here are some important roles to consider:

Administrator - The administrator should be able to support both the hardware and software involved as well as disaster recovery and some support (tier 3). This is sometimes split into two roles, with an infrastructure adminstator supporting the hardware/network side and an application administrator supporting the software and configuration. This person should be familiar with the configuration and maintenance of SharePoint 2010, SQL, Windows 2008 Operating Systems, networks, powershell, all third party tools,  backup and restore technologies, along with the different hardware and network configurations. 
Site Collection Administrators  - These are people who are responsible for the configuration of a site. They can make changes to the features, security, content, and more for a given site. They are also responsible for configuring search keywords, best bets, available scopes, and more. These people should be very familiar with SharePoint, SharePoint Designer, SharePoint Workspace, company security and auditing policies as well as any communications policies. 
Developer/Customizer - A true developer is always an added value to be able to enhance and expand the functionality of SharePoint. However, it is also irresponsible to exclude those who have the skills to customize without code. One or more of these positions might benefit an organization. They should be familiar with Powershell, SharePoint Designer, third party tools. The developer should add to this list .NET/C#, jQuery (the customizer may also be familiar with this).
Support team - This may or may not be a separate position, but would include people who have been trained on the use of SharePoint within your organization, access to a knowledgebase, and have solid troubleshooting skills. 

It is possible to combine these aspects even down to a single role, kind of a jack of all trades person, however, it is generally not recommended, and in some cases can cause you to be out of compliance with legal regulations (for example, the developer who develops a financial application cannot deploy said application, it must be done by the administrator for those institutions who must comply with Sarbanes-Oxley). It is also possible to outsource one or more of these positions to external sources such as consultants, and large support teams who can handle large volumes of calls. 
In any case, SharePoint can be a valuable asset to your organization, and should be properly staffed, but still meet your budgetary needs to realize that value. 

