Blog | Jul 16, 2013

Assembling the Right Team

In most organizations, implementing SharePoint has usually been executed as an “IT project” versus a “business project”.  This paradigm is beginning to shift to SharePoint implementations becoming a “business project” supported by the IT department.

As SharePoint becomes ubiquitous in organizations, more and more business users are joining the SharePoint implementation teams to ensure that business objectives are represented within the SharePoint environment.

With the increased number of business users and the importance of the role of business in a SharePoint implementation, the membership and dynamics of SharePoint implementation teams is changing and it is more important than ever to make sure you have the right resources involved to obtain the expected outcome.

When assembling your SharePoint implementation team (whether for a new implementation, upgrade, migration, or new features), you should consider the following teams:

• Management Team:  An Executive Sponsor, to handle communication with the Executive Leadership Team, and a solid Project Manager to handle the tactical and strategic aspects of the project.
• Architect Team:  A SharePoint Architect to design the logical and physical architectures of the SharePoint environment; Network Architect to ensure that network resources are available and adequate to support the SharePoint environment; and Database Architect to ensure that the database environment can meet the availability and capacity requirements of SharePoint.
• Requirements and Testing Team:  The Business Analyst will interpret business and technical requirements to ensure that the system meets end user needs that work within the confines of the available technology; System Testers to ensure that the system is operating according to the agreed-upon requirements.
• Development Team (if there is custom development work) to build custom code integrated into the SharePoint environment.
• System Administration Team:  A SharePoint Administrator to configure and administer the SharePoint environment as well as performs troubleshooting and communicating with end users regarding issues and end user training opportunities; SQL Database Administrator to configure the SQL environment and troubleshoot issues; and Network Administrator to configure and troubleshoot network issues that affect SharePoint.
• User Community:  A selected group of end users to participate in Proof of Concept (POC) – the end users who will actually represent the business regarding use of the SharePoint environment on a daily basis.  These are the most important team members as their feedback will be essential in order to successfully deploy SharePoint to a non-technical audience.

The role descriptions may vary slightly in your organization, however, the bottom line is that the executive leadership, Project Management Office (PMO), development staff, infrastructure department, and end users need to be represented in order to gain a holistic perspective of the business requirements and the value that SharePoint will bring to the organization.

We will blog more about the following areas in upcoming posts:

1. The Importance of an Upgrade Strategy
2. Leadership/Sponsor Support