- Understanding the SharePoint Server Roles
- Understanding the Reasons for Deploying Multiple Farms
- Choosing the Right Hardware for SharePoint
- Determining Optimal Operating System Configuration
- Planning for Database and Additional Software
- Examining Real-World SharePoint 2013 Deployments
- Addressing Common Business Issues with SharePoint Features
- Deploying a Team Collaboration Solution with SharePoint
- Deploying a Corporate Intranet Solution with SharePoint
- Deploying a Customer Extranet Solution with SharePoint
- Best Practices
Deploying a Team Collaboration Solution with SharePoint
A team collaboration site is used by a group of people working together for a common end result, or to complete a project. The success of the team or project depends on the effectiveness of the team and its ability to efficiently collaborate to complete the project. Therefore, the site is designed to facilitate team communications and sharing project information.
Usually, a team collaboration site is an internal, decentralized site that has a relatively small number of members. However, it can be configured to provide access for members external to the organization. When the site is implemented, it replaces the traditional file share-based storage, use of email, and use of other traditional applications the organization may have for storing and accessing documents and other information.
Outlining Business Needs for the Team Collaboration Solution
The general categories of business needs for this group are communications, project management, and document management. These needs can be mapped to SharePoint features, as presented in this section:
- Communications: Interacting with other team members electronically using workspace instant-messaging capabilities. Finding out when information has changed through the use of alerts. Having discussions on issues or documents using the general or document discussion components.
- Project management: Assigning major project tasks to individuals using a tasks list. Tracking and following up on tasks using a tasks list and various views of the list. Centralizing and distributing information such as objectives, agendas, and decisions for project meetings in one place using meeting workspaces. Providing status reports to management based on information in task items.
- Document management: Having a common place for storing documents by using shared document libraries. Managing document revisions using the check-in/check-out and version retention features. Controlling document publication using content approval. Enhancing the ability to find and feature specific documents by assigning them to topics and best-bets classifying documents for retrieval using metadata attached to the document.
Implementing a Team Collaboration Solution with SharePoint
The team collaboration site is implemented using a SharePoint team site. A shared document library is created in the team site for document management and a tasks list for assigning responsibilities. Content approval is enabled for the document library with the project manager assigned the role of approver. Document workspaces are also used for individual documents to incorporate direct access from SharePoint 2013 applications. The team uses document discussions to communicate ideas about document contents and a general discussion for items relating to the project. The team site is part of a SharePoint implementation that has content sources defined for searching relevant information and archived documents.
Outlining Ideas for Using the Team Collaboration Solution
This section includes some ideas to incorporate into the team site solution with the elements previously discussed. The major project milestone tasks can be entered into a tasks list, assigned to individual team members, and then tracked by the project manager. The tasks list can also be used for status reporting.
Users can initially create documents using Microsoft Office 2007/2013 applications and then save them to a document workspace. The document workspace can be used by the team members as a conduit for instant messaging on project-related issues. Discussions within the document can be used for providing feedback and recommendations for document content.
When the document is ready for publishing, it can be moved to the shared library where it is reviewed by the approver. The approver can set up an alert to be notified when the new documents are added or modified within the library.