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.
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!