In June this year, Paul Beck was looking for people who want to contribute a chapter to a SharePoint 2010 book created by the community. Seeing this as a good chance to share some of my experience with others, I wrote a chapter, in total we had 13 authors and thus 13 chapters.

The book was just published and is now available on as well!

To give you a better overview of the different chapters, here are the introductions for all of them (Links to the LinkedIn profiles taken from Veronique Palmer’s blog):

John Timney – Structuring a SharePoint 2010 Practice

SharePoint 2010 is quite simply ?nothing like SharePoint 2007?! It is vastly more scalable, significantly more complex, and hugely appealing as an information management hub. A consequence of the successful re-architecture of the product to such a strategic hub product and the core of the Microsoft tools strategy is that programmes and projects Employers and recruiters need to think carefully about the new range of planning roles and skill sets required to satisfy a successful ?end-to-end? delivery of SharePoint 2010.

Demand and salaries for SharePoint 2010 Professionals across the board have increased dramatically as organisations perform a land grab on experienced staff. They have realised that those better placed will not only weather this skills storm but also grab a host of emerging new business opportunities.

Unfortunately, few recruiters understand the complexities of delivery and the demands SharePoint brings to staffing delivery programmes or emerging Practices. Typically, neither do internal Human Resource departments. One could argue that this problem is even evident in Microsoft literature as Technet and MSDN also have little information published on how to fill this void.

This chapter seeks to address that by explaining the range of roles and skill sets required to build a successful SharePoint 2010 Practice, to plan for internal career progression and assist with staff retention.


Justin Meadows – SharePoint Test Environments

Test environments for most information technology professionals are a no-brainer — major system changes should be tested once, twice, even three times to provide the best possible experience to end users with little to no interruption in service. Recent virtualization technologies have made this easier than ever; one only needs to spin-up a new instance of a virtual machine and off they go with an entire SharePoint environment at their disposal.

SharePoint administrators will painfully learn, however, that this testing model does not adapt well to the componentized structure underlying a well-built SharePoint system. In this chapter we will review a few SharePoint system fundamentals, basic testing guidelines, and explore the case for building and maintaining a fully scaled test environment that is architecturally similar to an organization’s production environment. We will also discuss the justification for why an organization might choose to build more than one test environment.

Using one or more fully-scaled test environments is the only way to understand the implications of a major system change. These environments also provide a mechanism for rehearsing system changes. With such a tool at their disposal, SharePoint administrators can maintain and administer their systems with confidence.


Veronique Palmer – SharePoint Adoption

There is a common misconception that merely installing SharePoint makes for a successful implementation. It is how the people in the company effectively adopts the solution that is the true measure of success. Have you asked yourself how you will get the business to use the service?

Anyone can cope when there is only one table booked in a restaurant; but what happens when you are booked to capacity with a waiting list – are you geared to cope with that demand. What if you get no bookings at all? Could you explain to your investors why no-one is visiting?

SharePoint user adoption is about how to get to a full house, how to be prepared for the rush, and how to manage it once it happens.

People will not =magically’ adopt SharePoint, there are measures you need to put into place to ensure that happens. Do this correctly and you will have a very high adoption rate; and consequently good return on investment for the capital outlay of the infrastructure.

This chapter is for anyone responsible for a SharePoint implementation, whether in business or IT.


Jasper Oosterveld – Social SharePoint

The word =Social has become a very popular term over the last couple of years. Everyone is familiar with Facebook, Twitter and YouTube. These so-called Social sites attract millions of visitors per day! So how does this translate to SharePoint 2010? What Social features are available?

Social features were also available (albeit limitedly) in the previous version Microsoft Office SharePoint Server 2007 (MOSS 2007). The main feature was the My Site. This site is a personal page for every user within a SharePoint Intranet portal. The user was able to share valuable information with colleagues, such as a mobile number, e-mail address, manager or skills. Other users were able to use the MOSS 2007 search engine to find a colleague with the skill “Writing marketing material?, for example. By using these features, users were able to connect and share information with each other.

SharePoint 2010 improves on this and now more new features are available. This chapter describes these features, and how they can improve collaboration within your organisation.


Symon Garfield – The Art of SharePoint Success

Over the past five years, through engagements with hundreds of organisations, I’ve developed a framework for ensuring that investments in SharePoint deliv
er long term returns. This chapter is an introduction to the framework which consists of four key elements: Governance, Strategy, Transition and Architecture


Rene Modery – Exploring Different Options for Implementing SharePoint Solutions

An important decision to make while planning the implementation of any SharePoint solution is how exactly it should be created. Two commonly used options are leveraging the out of the box available functionality through customization in the browser and development of solutions using custom code.

SharePoint’s out of the box functionality empowers end users to create simple solutions with little effort and in a short time frame, however with a limited customization scope. Development of custom code solutions provides the most flexibility, however at a higher cost in terms of complexity and resource requirements.

Another option is to extend the standard SharePoint functionality with customizations that make use of JavaScript and the Data View Web Part. Using JavaScript has become a very popular way of extending SharePoint without having to rely on custom code. It allows users with some basic development knowledge to create their own more advanced solutions easily.

Considering all these possibilities, when evaluating the correct course to take for a solution implementation, organizations need to take into account the pros and cons of the different approaches, and weigh them against each other. This chapter will compare these approaches with each other and describe the capabilities, as well as the benefits and the drawbacks of each approach, allowing a decision maker to better understand which method is useful in which situation and choose the best option.


Paul Beck – SharePoint Server-based Data Storage and Data Access

This chapter guides readers through the basic storage and data access options available in SharePoint 2010 application development projects. The matching of application business requirements with the appropriate storage and data access technique is vital for achieving a successful project. We begin by contrasting SharePoint lists with SQL Server database storage. Thereafter, we shall consider using blob storage and web services for an agnostic storage provider. It is also necessary to consider the limitations of SharePoint to help better understand why particular storage strategies are preferable. Lastly, we examine various data access options that are available for server-side application development projects. SharePoint’s server-side object model is reviewed as well as LINQ, LINQ to SQL, LINQ to SharePoint, Web Services and Business Connectivity Services.


Suzanne George – SharePoint 2010 Automated Code Deployment

This chapter guides readers through a variety of SharePoint Code Deployment methodologies for 7×24 production intranet and internet facing farms. SharePoint farms requiring high availability often constrain and challenge the method of deployment and site administration due to customizations, full development and deployment documentation, and 100% reproducibility. In most deployments (old and new), the focus of planning and governance applies to the users and application management of power-users to ensure a deployment is successful immediately after an upgrade or new solution release. However, the same standards and planning guidelines should also apply to the SharePoint development lifecycle.


Conrad Grobler – SharePoint Security and Authentication Notes

SharePoint 2010 provides various options for user authentication as well as passing authentication information to external line-of-business systems. During the design and implementation of a SharePoint 2010 solution, the chosen authentication method could affect or restrict the availability of some SharePoint functionality and the options for interacting with external systems.

This chapter will discuss the different options and architectural considerations for user authentication and for further authentication to external systems.


Ashraf Islam – InfoPath 2010 – What is new?

This chapter is about highlighting the massive improvements incorporated in InfoPath 2010. The aim of this chapter is to provide enough information to the reader to be able to understand the products strengths and limitations. I will also review key information such as licensing that companies and decision makers must be aware of before selecting InfoPath as a form design solution.

InfoPath 2010 is fast becoming a mainstream product due to its integration with SharePoint 2010 however; it is unfortunate that there still exist some long trailing misconceptions about the product such as:

  • InfoPath web enabled forms need the InfoPath client installed on user desktop to be able to view forms.
  • InfoPath forms can only be designed in InfoPath Designer, etc.

These misconceptions will be reviewed and explained for the readers. This chapter covers points I see as being vital to implementing InfoPath SharePoint based solutions.


John Stover – Governance in SharePoint

Governance is one of the most popular words related to SharePoint today. For many, governance means management. Most people use ?govern? and ?manage? interchangeably. However, governance and management actually mean two different things, though they do go hand in hand.

Governance is a framework that defines strategic and goals and objectives. Governance defines who gets to make decisions, how decisions are made and how to communicate those decisions. Governance defines accountability and procedures for reconciling differences. Define governance in a documented
Governance Plan.

Management refers to the action, the processes, the editing process, and the enforcement of the Governance Plan.

Governance is worthless without management, and managing a SharePoint site without a governance strategy is trying to steer a rudderless ship. You have the tools, you have the personnel, and you will end up somewhere. But is it where you want to go?


Giles Hamson – Creating Dashboards using Business Connectivity Services, SharePoint Designer and other related technologies

This chapter guides readers into creating dashboards using some of the key technologies in SharePoint 2010.

Throughout my experience as a consultant, piecing together the various tutorials available on the web to achieve the dashboards Microsoft so heavily advertise alongside the SharePoint product can be daunting. This chapter aims to take you through from start to finish creating dashboards using the following areas:

  • Secure Store Service
  • External Content Types in SharePoint Designer
  • Business Connectivity Services (BCS), Business Data Catalog (BDC) permissions and actions
  • Dashboards including:
    Business Data, Filter & Excel Web Access web parts

Other technologies are available for creating dashboards within SharePoint including:

  • Reporting Services
  • PerformancePoint
  • PowerPivot
  • Visio Services
  • Chart Web Part
  • List Web Parts

These however will not be the focus of this chapter.


Mark Macrae – Building Business Intelligence Solutions with SharePoint 2010

Business Intelligence is an increasingly desirable commodity in the workplace. IT Managers wish to see how many support tickets are open, executives want to know how the business is doing against their key performance indicators – even I may want to see how much holiday I have remaining to use this year!

However, the answers to simple questions such as those above are rarely self-served, or answered in the timeframe you would expect. These questions often involve multiple people fishing through files or old emails, cutting and pasting figures in Excel or waiting on information to be fed through from an overseas office. Management are often frustrated that they cannot see at a glance how their department is performing without IT spending days developing a custom report, only to be re-engineered the next time the manager wants to know how his department is doing.

The solution to these common problems is a well designed and efficient business intelligence system, and a medium on which to surface dashboards tailored to the needs of the consumer. In the past, such systems have been expensive and generally aimed at the minority of users, however since Microsoft seriously entered the business intelligence market, a BI system can be implemented at an affordable price through SharePoint 2010 and its related technologies for the masses to enjoy.

This chapter explains how SharePoint 2010, and its large suite of business intelligence features, could be used to fulfil the needs of most business intelligence requirements in the workplace. We will explore the pros and cons of the feature set, and look at a couple of example use cases.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.