Sharepoint - Why a Framework Is Needed

Overview

This article will discuss an approach to using SharePoint to add value to an enterprise's operations, and then cover how you can be successful using SharePoint for optimizing your operations, using a framework called "AAA" (Activities, Assignments, Artifacts).

Why a framework is needed

To date, there have been a wide variety of approaches to rolling out SharePoint. At one end of the continuum is the "Wild West" approach, where there is little thought or planning around governance or information architecture. Typically this type of rollout is seen where resources are scare, and IT is told to "give us SharePoint". In a matter of hours, sites can be provisioned and users can be added to the site collection, and it won't be long before SharePoint is up and running and a harried IT manager can cross this implementation off of his or her list.

Anyone who has been in this situation knows what comes next- what is affectionately termed "Fileshare 2.0″, wherein users simply pull all of their documents into document libraries, create lists where they previously would have used spreadsheets to track things, and create sites that are data-rich but information-poor.

At the other end of the continuum is the "Locked Down" approach. This type of approach gives little control to end users, instead relying on a DBA type model where any changes or additions need to be performed by a typically overcommitted team of Sharepoint administrators. End users get frustrated with slow turnaround times for simple requests like the creation of a new list or document library, and SharePoint usage never gains momentum.

The AAA framework allows you to find the "sweet spot" on the continuum, using an approach that provides enough structure to insure good information architecture and findability, while allowing enough flexibility so that end users will not feel tied down or restricted while using SharePoint.

Why a no code approach is critical to the AAA framework

The AAA framework is a no code approach- there are no assemblies, solutions, or code to manage. The main reason for this is simplicity, and the fundamental consideration that a customized Sharepoint site introduces a level of complexity that may not be warranted from a cost/benefit perspective. An out of the box implementation with solid information architecture, using connected web parts and customized lists can deliver a robust framework for managing many typical business scenarios, and the AAA framework can help standardize the delivery of your sites so that they are consistent, maintainable, and useful.

Metadata and the framework

Metadata is critical to any successful SharePoint site, and the AAA framework