SharePoint User Adoption – Key things to mention for SharePoint 2013

SharePoint User Adoption – Key things to mention for SharePoint 2013

Excerp: “For those entrenched in trying to get information workers to buy into using SharePoint, SharePoint User Adoption seems to be a black art. In a way, it is because the kind of enticements and methods you use will be relative to the product that is being supplied. In reality, complexity of User Adoption is based on the breadth of the SharePoint solution being implemented.

This article shows the different types of people there are in terms of the User Adoption (which has a lifecycle), and attempts to identify the related high priority areas where you should focus your communication and training programmes. Note. The kind of users involved are ‘generic’; and therefore you should use this as a model for any SharePoint solution – irrespective of version. The key areas of SharePoint I will focus on relate to Information Architecture, Term Store, Search and User Profiles and in SharePoint 2013”.

The article I wrote for MSDN newsletter is located here:

http://blogs.msdn.com/b/ukmsdn/archive/2012/11/13/sharepoint-user-adoption-key-things-to-mention-for-sharepoint-2013.aspx

Some thoughts on process of building SharePoint solutions

Some thoughts on process of building SharePoint solutions

From a planning perspective, what are the very basic areas that one needs to think of when going down the route of creating a SharePoint solution, whether its a site, or farm, or even a workflow solution. I have attempted to answer this by building a presentation key covering planning, adoption, supporting, delivery from a high level.

(more…)

My Books

My Books

I’m focused on SharePoint, having been involved since SharePoint 2003 hit the streets. All of my books are dedicated to SharePoint Implementation, Service, Support, Automation and SharePoint teaching. Click any of the links below to find out more about the books I have published:

Managing and Implementing SharePoint® 2010 Projects

MOS 2010 Study Guide for Microsoft® Office SharePoint®

MOS 2010 Study Guide for Microsoft® Word Expert, Excel® Expert, Access®, and SharePoint®

Microsoft® SharePoint® 2013: Planning for Adoption and Governance

Additionally, I was technical author for the following two books:

MOS 2013 Study Guide for Microsoft Office SharePoint

Creating and Implementing Microsoft SharePoint 2010 Real-World Projects

I am editor for the Software Best Practice Development Journal here.

Value Engineering in SharePoint – Part 3

Value Management in SharePoint – Part 2 of 3

In this second of a three part blog I will describe Value Management in SharePoint and how it can be applied when creating or implementing a new SharePoint solution. Note that in fact this can also be applied to existing SharePoint environments where there is a requirement to extend or enhance SharePoint.
Ten Steps to a successful implementation of SharePoint

Ten Steps to a successful implementation of SharePoint

People have been requesting me do a shortened article to cover SharePoint Implementation from a higher level; a kind of whats my the key steps required to deliver SharePoint to a client. Please note there’s a whole bunch of webcasts coming soon to go into some more detail on each of the steps, so watch this space. If you need further information go ahead and give me a shout! Happy Reading!

 

(more…)

Service Delivery – Working in harmony with external SharePoint agencies

Service Delivery – Working in harmony with external SharePoint agencies

Time for a service delivery article, looking at working with external SharePoint agencies in a SharePoint environment in BAU…

If you are operating and managing SharePoint environments for your clients, you may find that there is a business requirement for enhancements or modifications to something to take place which would alter your controlled SharePoint environment. This business requirement may be one where there is a call for the intended work to be carried out by utilising services from an external ‘SharePoint’ on a sub-contracted basis.

(more…)

SharePoint Archive Planning Guide

SharePoint Archive Planning Guide

History has a way of repeating itself. Thankfully, when we learn from the mistakes of the past, we are able to address new challenges more quickly and in smarter ways. In the early 1990s, email emerged as a collaboration mechanism, speeding up communications between multiple parties.

(more…)

Service Delivery – Working in harmony with external SharePoint agencies

Service Delivery – Working in harmony with external SharePoint agencies

Time for a service delivery article, looking at working with external SharePoint agencies in a SharePoint environment in BAU…

If you are operating and managing SharePoint environments for your clients, you may find that there is a business requirement for enhancements or modifications to something to take place which would alter your controlled SharePoint environment. This business requirement may be one where there is a call for the intended work to be carried out by utilising services from an external ‘SharePoint’ on a sub-contracted basis.

(more…)

SharePoint Governance

SharePoint Governance

SharePoint governance is not a hardware, software, or people resource solution. It is an organizational strategy and methodology for documenting and implementing business rules and controls related to your client’s data. It brings cross-functional teams together to identify data issues impacting the company or organization.

(more…)

Do you UAT SharePoint Standard Features?

Do you UAT SharePoint Standard Features?

Got a query today concerning User Acceptancy Testing (UAT) on SharePoint. As a SharePoint implementator, we know that the client needs to test the provision (your deliverables) of the SharePoint environment, based on exactly what they requested (the scope).

However, some may think that simply carrying out testing on just what the scope entails covers a full UAT.

Take this scenerio – the client is brand new to SharePoint, wants the product and needs to make sure that the team sites can store compliance data.

Do you UAT just the team site in terms of storing compliance data? No – the client doesn’t know SharePoint!

Another scenerio – the client is upgrading from SharePoint 2007 to 2010, wants the product and needs to make sure the team sites can store compliance data.

Do you UAT just the team site in terms of storing compliance data? No – the client needs to understand the nature of SharePoint 2010 against 2007 – they are not the same beast!

Of course, it all depends on whether the UAT is solely technical, or business oriented; for example, the UAT may simply be part of handing over support of the product into Business As Usual (BAU).

In anycase, UAT is perceived as something that guarantees the using the product of the product – the client is comfortable and convinced that the product does what it says on the tin. When implementing SharePoint you push the features of SharePoint; hence, you have documented standard sharepoint functionality. That must be conveyed that it works from a demonstratable perspective. Therefore UAT is required for standard SharePoint functionality.

That said, some clients might steer you away from this because in their view all they are interested in is the bits they asked for from SharePoint beyond what they ‘know’ / what they ‘think’ it does out-of-the-box. Beware of this approach since they may be assuming too little, too late.

In my experience I always UAT standard sharepoint since remember the element of training locks into this and it gives you invaluable insight into what the client expects to do with the product in their workplace. You should remind your client of this as it will instill in them the importance of understanding the nature of the beast!