Today I attended a session for the CSPUG (Chicago SharePoint User Group) hosted in the AON Center with Guest Speaker Joel Oleson.
Topic: SharePoint Governance
Key Takeaways: 10 Things, and these are paraphrased from Joel’s presentation. For all the details, slides and his notes, visit his blog here
Steps to Success in SharePoint
1. Confront Reality
- How does SharePoint fit into our business?
- Internal IT Road map
- How is SharePoint the answer, or not
- If not why?
- If it is the answer, we need a mission or directive as to why
- How is SharePoint the answer, or not
2. Create a Governance Plan
- Define a Service, SharePoint is a “service” based offering
- Service: Defined as, something you offer your users
- Define a team
- You will need a core group to tackle management of SharePoint and its policies
- Create ability to scale
- Don’t lock yourself small. Think big. It has to have the ability to breathe over time.
- Need a plan
- Without a plan, failure is eminent
- Use your team to create a governance plan and policies and stand behind them.
- Can help avoid SCOPE CREEP
3. Get an executive sponsor
- Budget, your sponsor will be your biggest advocate and often dictates this number.
- Success, they stand behind you and some times in front to help pave the way.
- High-level advocate and voice for you, can garner additional “C” level support
4. Create the “Dream Team”
- Stakeholder (Business Team, Executive Sponsor, etc)
- Project Management Team
- IT/Systems Group
- Business Rep’s from Firm, your test case group, etc
5. Build Services, not “Stuff”
- You are an ISP
- You are hosting “something” Intranet or Internet
- Don’t let the business run YOU, YOU need to run the business by delivering your services
- Also, you must be able to scale your services
6. Clear Policies & Standards
7. Invest in Scalable Information Architecture
- Figure out limits
- Find pitfalls with large scale
- Example
- i.Site v. Site Collection
- Understand all objects and make proper decision process for scale
8. Don’t forget about Change/Risk management!
- Take Hot fixes seriously
- In single box environment. Use images to do all testing before applying to production!!!
- In a multi-box or large scale farm, you BETTER have a replicated development environment.
9. Adoption is what COUNTS
10.Keep it Simple Stupid!! KISS
There are my takeaways and comments! BE sure to visit Joel’s blog for the full deck and if you have questions, hit me up on twitter @IntranetBuilder
Cheers


