• Home
  • What We Do & Featured Services
  • About Us & Our Work
    • Our Case Studies
    • Join our team!
  • Contact Us
Microsoft SharePoint & supporting technologies blog
← Yammer and SharePoint integration options
Microsoft SharePoint and the Gartner Magic Quadrant in 2013 →

Planning for a SharePoint ‘Business as usual’ service

Posted on July 30, 2013 by boris

Business as usual (BAU) service

It’s a sign of a sensible and mature approach discussing planning for a SharePoint  ‘business as usual’ service, at the beginning of the project and not as an afterthought following launch.

Microsoft SharePoint has become the de-facto standard for many medium to large enterprises over the last 3 years, with many of the most recognised brands investing in the popular technology in some capacity. Although a couple of years old, the following visual we think, speaks for itself.

Planning for a SharePoint ‘Business as usual’ service?
View full image

What those numbers won’t tell you is how many SharePoint projects have failed to deliver the perceived benefits, much touted at the beginning.

A significant reason for this we think is an often overlook aspect of deployments we come across, which is that of budgeting for the activities, processes and resources that will be need to be in place, when SharePoint becomes a ‘business as usual’ (BAU) service, following its launch.

It’s often all about what it takes to implement the platform, not what it will take to support, maintain and derive the most out it in the future. Hence why we recommend you absolutely have this in your plans, even if you scale back your ambitions due to time or budget constraints.

What should you plan for?

Planning and delivering a robust BAU service can be a large, expensive and challenging activity and the success of which is in our experience is largely driven by some of the following:

  • The demands of the business stakeholders – What type of support service do they want? What are the response times to calls?
  • Scale of the budgets (heavily influenced by the size of the organisation) – How much can they afford to fund in addition to the existing project deliverables?
  • Success factors agreed by the project stakeholders and sponsors – Is the BAU support service one of the key measures?
  • How seriously the business aligns this service (and underlying technology) to its strategic objectives – Is this a tactical solution or of strategic importance that needs to be back by a robust investment profile?
  • The approach taken to implementing and planning for change after it’s launched – How have you approached the topic of governance, how do you plan to manage change? Who will own platform roadmap from the business (it shouldn’t be IT!)
  • …and arguably the local teams own skills and experience on what to plan and provide for here – What resources and skills do we have and or need? How do we manage change requests for the platform – think content, configuration and custom (three types of change on a SharePoint platform).

This can be something as simple as providing some administrator training to your existing support staff to deal calls and resolve them. To something a lot more involved around working with existing but outsourced operational and tactical support teams who are working with ITIL or other service and support frameworks, or a full blown team of internal resources often referred to a ‘Centre of Excellence’.

The latter’s existence is a relatively immature model, but is often underpinned by some form of platform steering committee. Its primary objective is to deliver a rounded service that thinks and acts both strategically and operationally in managing the platform, both on the day to day aspects, but also the future manageability and roadmap updates to the SharePoint platform. This is often joined up with related technologies like Microsoft Exchange and Lync services under the same ‘collaborative’ roof, with many larger organisations and is something we’ve been working with actively in setting up with some of our larger clients for several years now.

So in summary, introducing some form of BAU service is something you need to actively consider from the outset of your planning, and budget accordingly. If you don’t, you will seriously damage the credibility of the platform to be taken on by the business, as they will need support on an on-going basis, which if not received, will force them back to their previous ways of working or something else entirely.

If you are looking for advice on understanding more about this topic, get in touch by email or give us call with further details.

Related Posts

  • Microsoft SharePoint and Gartner Enterprise Content Management (ECM) for 2013Microsoft SharePoint and Gartner Enterprise Content Management (ECM) for 2013
  • Did you achieve your SharePoint ROI?Did you achieve your SharePoint ROI?
  • Older versions of SharePointOlder versions of SharePoint
  • Keep your SharePoint and IT strategy in syncKeep your SharePoint and IT strategy in sync
  • Yammer and SharePoint integration optionsYammer and SharePoint integration options
Zemanta
This entry was posted in SharePoint, SharePoint 2013, SharePoint Business Case, SharePoint Governance and tagged SharePoint, SharePoint 2010, SharePoint 2013, SharePoint Governance. Bookmark the permalink.
← Yammer and SharePoint integration options
Microsoft SharePoint and the Gartner Magic Quadrant in 2013 →

Comments are closed.

  • Search…

  • Recent Posts

    • MS Office 365 Public Roadmap announced today June 20, 2014
    • SharePoint Intranet – 12 Signs why you may need one February 14, 2014
    • Microsoft SharePoint and Gartner Enterprise Content Management (ECM) for 2013 January 27, 2014
    • Microsoft SharePoint and the Gartner Magic Quadrant in 2013 August 31, 2013
    • Planning for a SharePoint ‘Business as usual’ service July 30, 2013
  • Categories

    • 3rd Party Products
    • BPOS
    • Business Case
    • Casestudy
    • Exchange Online
    • Extranet
    • Intranet
    • Licensing
    • LinkedIn
    • Lync
    • Miscellaneous
    • MOSS
    • Office 2007
    • Office 365
    • Office 365 Roadmap
    • SaaS
    • SharePoint
    • SharePoint 2010
    • SharePoint 2013
    • SharePoint Architecture
    • SharePoint Business Case
    • SharePoint Design
    • SharePoint Governance
    • SharePoint Migration
    • SharePoint Online
    • SharePoint Resourcing
    • Uncategorized
    • User Experience
    • WorkShares
    • WSS
    • Yammer
  • Tags

    BPOS Codename Oslo Extranet FAST gartner Hosted SharePoint Licensing LinkedIn migration Miscellaneous MOSS Office 365 Office 365 Public Roadmap‬ Office 365‬ Office 2007 Office Graph Outlook 2007 ROI Search Secure File Transfer SharePoint SharePoint 2003 SharePoint 2007 SharePoint 2010 SharePoint 2013 SharePoint Architecture SharePoint Consultancy SharePoint Governance SharePoint Integration SharePoint Online SharePoint Project Management SharePoint Resourcing user engagement user experience works WorkShares WSS yammer
  • Archives

    • June 2014 (1)
    • February 2014 (1)
    • January 2014 (1)
    • August 2013 (1)
    • July 2013 (1)
    • May 2013 (1)
    • April 2013 (1)
    • March 2013 (2)
    • February 2013 (2)
    • January 2013 (1)
    • December 2012 (3)
    • November 2012 (1)
    • August 2012 (1)
    • March 2010 (1)
    • January 2010 (1)
    • November 2009 (1)
    • September 2009 (2)
    • July 2009 (1)
    • June 2009 (1)
    • May 2009 (1)
    • April 2009 (2)
    • March 2009 (1)
    • February 2009 (1)
    • December 2008 (3)
    • November 2008 (2)
    • September 2008 (1)
    • August 2008 (3)
    • June 2008 (1)
    • April 2008 (2)
    • November 2007 (1)
    • October 2007 (1)
    • September 2007 (3)
    • August 2007 (3)
    • July 2007 (3)
    • May 2007 (2)
    • April 2007 (2)
    • March 2007 (2)
    • February 2007 (2)
Microsoft SharePoint & supporting technologies blog
Blog powered by WordPress.
Joomla! extension by 'corePHP'

Contact Info

WorkShares Limited

W: www.workshares.co.uk
E: This email address is being protected from spambots. You need JavaScript enabled to view it. This email address is being protected from spambots. You need JavaScript enabled to view it.
T: +44 208 133 1599 
Company Reg. No. 5995876
© WorkShares 2020  Disclaimer

Microsoft Partner

VAT Reg. No. 901 9112 60
Our LinkedIn page for WorkShares WorkShares Google+ site Call us on SkypeOur Facebook page for WorkShares This email address is being protected from spambots. You need JavaScript enabled to view it. This email address is being protected from spambots. You need JavaScript enabled to view it.