SharePoint Governance (PKS) Part Trois.
I wanted to talk briefly about a specific project and how it might be implemented while keeping the governance considerations mentioned in the
last 2 posts top of mind.
In my view, if we had an engaged Business Strategy team the strategic instructions would look something like this. Developing people is a critical activity to ensure the future success of our company. Training is a crucial component of developing people and it’s imperative that we find a more cost effective way to deliver this training. We must also continue to leverage our investment in SharePoint and continue to work towards making it our primary platform for delivering rich media and interactivity.
However, really how it went was more like: It would be cool if we could have streaming video for stuff like eLearning. These comments and conversations were casual but repeated and were initiated prior to the kick-off of the governance project.
We were keenly aware of a few things:
- People Development and Training is a strategically important area for our company
- Costs of delivering training must be reduced – especially considering the current economic climate
- We have invested heavily in SharePoint as both a communication,collaboration and application platform and need to continue exploit that investment
- There has been an expressed desire to slowly start introducing Enterprise 2.0 ideas and capabilities to the organization.
- Our executives have been blogging and slowly introducing more supporting media to their posts
- The next step will almost certainly be executive podcasting
- Allowing for ranking and commenting on content is a simple way to increase the interactivity of the portal and generate more feedback.
As the Manager of Global Business Solutions I had my team download and install the SharePoint PKS on our SharePoint development environment. Configuration and testing took a few weeks and as soon as it got to a reasonably demonstratable state we assembled our Technology team and a SharePoint Business Analyst from the People Development and Training department (the functional owners of the portal).
We spent a few days putting detailed documentation together on what it would take to implement the PKS in production based on the information we had (which was very little). Our objective at this point was to think through the possible implications but to also stress to the Business Strategy team that this was a significant undertaking. The documentation covered the following main areas:
- Business Opportunity and Objectives
- Prerequisites
- Infrastructure Requirements
- Policy and Guideline Requirements
- Estimated Project Costs (this was a WAG)
- Ongoing Costs
- Resource Requirements
- Risks
- Potential Success Criteria and KPIs
Point 2 relating to prerequisites are where the governance piece comes into play. Whilst the governance development is well underway, the teams are currently working on their action items – some of which are related to training, acceptable use, SLAs, disaster recovery etc. We stridently insisted that these must be approved and in place before introducing more complexity to our SharePoint implementation.
We demonstrated the software to the Business Strategy team members and reviewed the documentation with them. It is currently in their hands and we’ll see in the near future what the decision is. As I have stated previously, this is the approach we have decided to take. Proactivity on the part of the Technical Strategy team to look forward and initiate projects that we believe have business merit and bring those to the BST for approval.
Popularity: 28% [?]