This document discusses how to effectively govern SharePoint content, deployments, and customizations. It emphasizes that SharePoint governance is important to manage content findability, environment consistency and stability, and team coordination. The solution involves implementing governance best practices and clear leadership. It recommends defining roles and responsibilities, managing the information architecture and infrastructure, and using techniques like solution packages for code deployment.

1. HOW TO EFFECTIVELY GOVERN
YOUR SHAREPOINT CONTENT,
DEPLOYMENTS, AND DEVELOPER
CUSTOMIZATIONS
SHAREPOINT DEPLOYMENTS CAN BE DIFFICULT TO MANAGE, ESPECIALLY IF YOU
HAVE A LOT OF CONTENT. CHAOS CAN REIGN, ALL THE WAY FROM
CONTENT FINDABILITY, TO ENVIRONMENT CONSISTENCY AND STABILITY, AND HOW TO
BEST COORDINATE YOUR TEAM. THE SOLUTION LIES WITH
IMPLEMENTING GOVERNANCE BEST PRACTICES AND GOOD, CLEARLY DEFINED
LEADERSHIP. COME LEARN HOW TO CONTROL THE CHAOS!
Phil Wicklund
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

2. About Me?
Training & Certifications:
• MCTIP: SharePoint 2010 Administration
• MCPD: SharePoint 2010 Development
• Microsoft’s SharePoint Masters Training (Redmond, WA)
Other Notable Experience:
• Published Author on SharePoint 2010 (SharePoint 2010 Workflows in
Action)
• National Speaker at SharePoint Conferences (The Experts Conference-LA,
SharePoint Technology Conference-San Fran, TechFuse-MN,
SharePoint Saturdays)
• SharePoint Blog: www.philwicklund.com
About Me: Over 6 years of experience SharePoint Architecture Experience, trained
SharePoint architecture and development classes for nationally renown SharePoint-
focused training organization.

3. Agenda
 Common Pain Points (End Users/Admins, &
Architects/Devs)
 Governance Strategies
 Managing “12 Hive” Customizations
 Code Promotion Techniques
 Instructor Led Demonstration
 New Visual Studio project
 Simulate common 12 Hive modifications, including
demonstrating how to:
 Build a “Hello World” .NET web part
 Wrap that web part with a Feature
 Add custom actions into the UI
 Deploy these customizations with a SharePoint Solution
Package
 Conclusion
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

4. Common Pain Points
 Findability
 Maintaining an Information
Architecture
 Viral Growth
 Retention
 Security & Risk
Management
 Adoption
 Training/Support
 Capacity Monitoring
 Lack of Vision / Quagmire
 Version Control
 Overwriting Work
 Front End Consistency
 Team Member
Consistency
 Too Few Environments

 Stability/Promotability
 What Changed, Why,
and When
Administrators / Power End
Users
Architects / Developers
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

5. Administrative Pain Points?
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

6. Environment Governance
Strategies
 WHAT areas need to be governed?
 Taxonomy / Information Architecture
 Physical Infrastructure & Platform Services
 HOW will we govern?
 How will we hold ourselves accountable?
 WHO will it be governed by?
 What Roles are in Play?
 What skills are needed?
 WHY are we doing this?
 End user adoption… (ROI)
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

7. WHAT: Taxonomy & IA
 The BIG 3:
 Who are our users?
 What are they trying to do?
 How will they do it?
 Information Architecture –
Where does this go?
 Document Compliance
(security & retention)
 Search (Best bets,
keywords, usage,
relevancy)
 Standards, Templates, and
Site Versioning
 New Site Request
Management (Viral
Growth)
 Support Tiers
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

8. WHAT: Infrastructure
 Goal: Environment Governance
Plan
 Stability
 Consistency
 Promotable
 “Too few Environments”
 Content Database Scaling &
Monitoring
 “Technical Taxonomy”
 Server Load (CPU, Memory,
Local Disk, etc.)
 Disaster Recovery
 Customizations
 Documentation

9. HOW: Board(s) of Governors
Adoption
Starts
Here!
• Who? What? How?
• Vision Statement
• Championship
• Product Roadmap
• IRM
• Policies
• Findability
• Taxonomy
• Capacity
• Disaster Recovery
• Training / Support
• Customizations
• Project Execution
• Content Good/Bad
• Q&A
• Best Practices
• Demonstrations

10. WHO: Roles & Responsibilities
 Product Manager
 Content Managers
 Product Manager
 Technical Architect
 Database Architect
 Findability Architect
 Compliance Architect
 Change Manager
 Training Manager
 Support Manager
Board of Content Managers
IT Governance Board
Policy Governance Board
 CIO
 Product Manager
 Enterprise Risk
Management
 Business
Stakeholders
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

11. WHO: What Skills are Needed?
Level 0
(End Users)
• Uploading
Documents
• Discussion
Boards
• MySites
• Tasks & Issues
• Calendaring
• Blogs
• Search
Level 1
(Content Managers)
• Level 0 plus…
• Creating Sub
sites & pages
• OOB Web Parts
• OOB Workflows
• Templates
• Site
Administration
• Managing
Security
Level 2
(Product Manager)
• Level 1 plus…
• “Theory” and
“Why”
• Trainer Acumen
• OOB vs.
Custom
• SharePoint
Designer
Workflows
• Site Collections
Level 3
(Architect)
• Level 2 plus…
• .NET Developer
• ASP.NET
Experience
• SharePoint
Development
Experience
• Custom Web
Parts
• Branding Dev.
• Workflow Dev.
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

12. WHO: What Skills are Needed?
Level 1.5
(Compliance Architect)
• Level 1 plus…
• “Theory” behind
security
• Broken
Inheritance
• Central Admin
Policies
• Security Auditing
• Search Security
Level 2.5
(Findability Architect)
• Level 2 plus…
• Search Center
• Crawler settings
• Content Sources
• Search Scopes
• Best Bets
• Usage Analysis
• Noise Words
• Search Security
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

13. WHY: Phil’s Phantastic Phormula Phor
Success
 if (Leadership == true)
{
if (Governance == true)
EndUserAdoption = true;
}
if (EndUserAdoption == true)
ROI = true;
if (ROI == true)
SUCCESS = true; // !!!!

14. Circling Back…
 Findability (I)
 Maintaining Taxonomy
(I)
 Viral Growth (C)
 Retention (P/I)
 Security (I)
 Risk Management (P/I)
 Adoption (P/I/C)
 Training/Support (I/C)
 Capacity Monitoring (I)
 Lack of Vision
(P)
 Quagmire (P)
Pain – Point
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

15. Developer Pain Points?
 Version Control
 Overwriting Work
 Front End Consistency
 Team Member Consistency
 Stability/ Promotability
 What Changed, Why,
and When – Rollback?

16. INSTRUCTOR LEAD
DEMONSTRATION
Using Visual Studio to deploy
SharePoint Customizations
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAConsulting.com

17. Conclusion…
 Phil’s Phive Phindings…
1. Identify your vision, roadmap, and risks
2. Identify appropriate roles & accountabilities
3. Govern 1 & 2 accordingly
4. Budget for Dev and Test environments
5. Use Solution Packages for code deployments
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAconsulting.com

18. QUESTIONS & COMMENTS
Phil Wicklund
SharePoint FREEWARE
www.PhilWicklund.com
SharePoint CONSULTING
www.RBAConsulting.com