This is a series of 9 articles. Click here for the full TOC
After we've talked about Roles and Responsibilities, now it's time to talk about how you want to staff people around SharePoint and then map the teams to identified people. The model can vary from a place to another.
One more commonly overlooked component of a successful implementation is staffing. Architects and administrators usually do a good job creating a bill of goods for hardware and software, but they often forget to secure funding for personnel to adequately develop and maintain systems. SharePoint can consume a large amount of human resources if used to its full potential. Understand what types of dedicated personnel are required in the beginning, and start getting stakeholders' support immediately. The table below offers a suggested staffing schedule for you to consider. (Note: F = One full time person and P = One part time person.)
Staff position
Medium to Large farm
System Administrator
P
Backup Administrator
SharePoint Farm Administrator
F
SQL Administrator
Active Directory Resource(s)
Enterprise Site Collections Administrator
P F
Enterprise Security Administrator
Site Owner
Developer
Product Management
Program Management
Architecture
Tester
User Experience (SharePoint Designer)
Release / Operations
Role
Owner
Secondary
SharePoint Team
Operation Team
Support Team
Intranet Portal
Site 1
Site 2
Site 3
Con't
Development Team
User Experience
(SharePoint Designer)
Operational Team
Read Next: about Training and Readiness
SharePoint Governance – Staffing and People Mappings - Code Eater (Wael A. Kabli) - Site Home - MSDN Blogs