In a recent UK Government report entitled ‘ Records management in SharePoint 2010: implications and issues ’ the report states the following areas where SharePoint needs to be either governed very tightly, or utilize the services of a 3rd party tool. The remainder of this post discusses each issue (raised in that report) and attempts to mitigate or provide a workable solution - most of which require custom development or the procurement of 3rd party software
However, other I.T. staff will occasionally enter problem incidents directly when they discover an issue before it is noticed by business units
So when we asked, “What are your three biggest on-going business issues with your SharePoint system,” #1, given by 46% or respondents, is the lack of expertise to maximize its usefulness, closely followed at #2 by the lack of strategic plans on what to use it for and what not to – hence the “unplanned and under-developed” title to this piece
Also, in the “On-going Issues” p. 4, 46% felt a “Lack of expertise to maximize its usefulness” is the biggest on-going issue and almost 40% felt there was a lack of strategic planning
What set of external circumstances did this “governance project” have in terms of political landmines, possibly the business or I.T. having issues with the development department(s) or even the parent company who “owns” the top level SharePoint farm but a division or partner firm wanting to stand-up their own specific SharePoint farm to meet requirements or a timeline that the parent company cannot meet
There are several factors that influence an organization’s decision regarding which architecture (that is, on-premises private cloud, public cloud, or hybrid cloud) they are going to design and implement for their short-term and long-term SharePoint roadmap needs, such as these: • The overall size of the organization and user base • Security issues • Legal and compliance issues • Any project or deployment time constraints • Complexity of customers’ current environment • Physical locations • Current identity infrastructure • Current IT infrastructure model and future IT roadmap • Network bandwidth issues • Software/hardware issues • Any vendor service level agreement (SLA) • High-availability/backup issues • Internal resource issues and related training • Support alignment • Service reporting • Standards adoption and management • Development alignment • Infrastructure alignment • Development platform management • Governance User issues Management and tools Development standards creation Information architecture and search Business requirements Infrastructure guidance When you are taking complex environments into consideration, there are also items such as these: • Multitenancy (Office 365 issues when a user goes outside of IT to create a new “environment”) • Multiple farms • Security (FBA, SAML claims, extranets) • Global clients with PHI, PII, Safe Harbor, intellectual property, EU pushback, or NSA concerns due to recent news It is key to also look at your current operations and how well your organization will be able to adapt to change
To re-iterate a bit from Nick and Christian’s posts, the whole reason for these commentaries was based on something Jeff Teper stated at the recent SharePoint Conference, which was as follows: Governance is not an issue in SharePoint 2010
External Authentication External authentication, which users both S2S and OAuth, is utilized for server-side code in the “remote web” and issues CSOM or REST API calls against the SharePoint host
v=510477178977350 just don’t blame it on SharePoint please) I am going to try and take a very serious topic and try to make light of major issues while posing questions that you should ask of your organization and put it on your organization’s radar screen ASAP!
no search term matches found in comments.
These issues range from loss to theft, or even taking of personal information or corporate trade secrets...Work with stakeholders and content authors to prioritize areas for improvement and address issues and concerns