Customizing governance


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Customizing governance

  1. 1. SharePoint Customizing Governance PLAN BEFORE CUSTOMIZING2013, Alexander Ahrens | MCPD exxlence
  2. 2. Why a customizing governance?  Complex customizings require a lot of Know-How and experience  Some customizings are not cloud compatible  Some customizings block system updates  Complex customizings are expensive in development, testing and operation  Avoid unnecessary customizing  Migrating a SharePoint with serverside customizings is a lot more expensive than migrating a SharePoint without serverside customizings
  3. 3. Types of Customization User Customization  Lists, Libraries, Views, Columns, Metadata, Fields, Page Layouts, Web Parts, formatting Text and Graphics, Site Pages, Wiki Pages Power User Customization  Connected Web Parts, SharePoint Store Apps, HTML in calculated fields, Workflows, JavaScript Developer Customizaion  Farm and Sandbox Solutions, Apps, Client side development
  4. 4. Microsoft:Use OOTB whenever possible  While designing the next wave, our team met with hundreds of customers and partners around the world which influenced not only the evolution of the product but also the guidance that we will update in this blog and on MSDN and TechNet. I wanted to emphasize two points as we roll- out the new release:  Use SharePoint as an out-of-box application whenever possible - We designed the new SharePoint UI to be clean, simple and fast and work great out-of-box. We encourage you not to modify it which could add complexity, performance and upgradeability and to focus your energy on working with users and groups to understand how to use SharePoint to improve productivity and collaboration and identifying and promoting best practices in your organization.  Be thorough in custom web design, development and testing – We know many SharePoint sites are published portals or custom web apps and are excited about the new features we designed for these scenarios. We encourage you to review the new features and guidance to reduce the amount of custom work you need to do. But even there, code is code and we encourage you to validate your design early in your development cycle and with particular focus on peak usage performance testing for how your customizations impact HTTP and SQL Server roundtrips. We have guidance and page and object caching techniques that can help here. Source:
  5. 5. Golden rules  Learn SharePoint features and capabilities before going with customizing.  Start client side customizing and app development before going with farm solutions.
  6. 6. The levels of customizing  I defined 5 levels of customizing that… 100 500  describe what types of solution elements are allowed  allows to classify every solution  describe what the consequences are by allowing certain levels of customizings
  7. 7. Levels of SharePoint Customizing Complex 500 Farm Solutions 400 Provider Hosted Apps, Silverlight Solutions BCS Solutions, Masterpages, Page Layouts, Designes and Themes, 300 SharePoint hosted Apps (HTML5 + JavaScript) 200 Access Services, InfoPath, SharePoint Designer Workflows Simple 100 Browser based solutions
  8. 8. Level 300 Governance 300 What? Why?  No server side customizings  High system stability  No provider hosted apps  No maintenance due to customizings  JavaScript as programing language  No separate infrastructure for testing of customizings required  Deployment via Sandbox Solutions  System remains on upgrade path  Rollout via PowerShell  Cloud compatibility is kept  Requires less Know-How for testing and operations than level 400+ governance
  9. 9. Level 400 Governance 400 What? Why?  Based on Level 300 Governance  Keeps all benefits of level 300 governance  Allows Hosted Apps and Silverlight  Allows more complex applications  Silverlight is hosted within without affecting system SharePoint operations  Hosted apps are hosted outside of  Requires more Know-How for SharePoint integration and security during  Hosted apps integrate in look and operations feel and navigation  Requires more Know-How for development and testing
  10. 10. Level 500 Governance 500 What? Why?  Based on Level 400 Governance  Complex solutions that cannot be realized with level 400 governance  Allows Farm Solutions are now possible  Allows maximum of customizing  Requires a high level of Know-How in operations, development and testing  Requires seperate infrtastructure for testing of customizings
  11. 11. Coding conventions andDeveloper Guidelines What? Why?  Define allowed features  Ensure that others can understand  Exclude features and improve custom solutions  Define rules for feature use  Ensure that technologies are used  Define naming conventions for their purpose  Capture good/best practices for reuse  Avoid unnecessary costs in support  Documentation rules and operations Examples:  InfoPath cannot be used because of licensing conditions  Apps may only use JQuery UI Version 1.7.1
  12. 12. Customizing levels in a multi farmfarm architectureIt makes sense to assign different levels to different farms:Collaboration and Service Farm Publishing Site Farm Level 300 Customizing  Level 500 Customizing Farm Solutions are used for  Farm Solutions for heavy Master Page deployment customizing and only. deployment of artefacts.Stays on upgrade path. Needs a lot developer assistance during upgrade.