To sum it up if you feed evil…evil will win.If you feed good…good will win.So if you don’t start out following best practices chances are you never will.
Design –Is the artistic style or appearance of a page.Branding – Is a strategy that goes behind the scenes to achieve the goal of the site.
511 surveyrespondents1. 57% had already upgraded to SP2010 within 14 months. Largest and earliest adoption seen.Customer-facing sites and custom applications are the least used.Took longer than expected to implement3Qtrs of the respondents said IT and the business users were satisfied. Customers tolerated the hassles of the implementation because the business value outweighed them.
The great contradiction…same articleSharePoint is awesome it does all these great things and it delivers applications fast!!Further down….the more customizations you add to your SharePoint farm the integrity of your farm goes down and stability and performance issues can occur…and let’s not forget the hassle of migrations.
Discussion area!!Who decides in your company?Should this be a question?Shouldn’t this already be stated somewhere?
Add\\Remove Announcements – Only able to update using SP Designer, User had no documentation and not contact.Template needs to be reusable… Hard coded all the URL’sUsers who are they? What do the users know?? (Seriously that was said to me!!)Customer wanted to update a link in their site… SP Designer, custom permissions, no documentation and again no contact for assistance.Packaging? What’s that? Do you mean a site template?Over doing Social Media….Yes it is powerful but be careful and lock it down.
Site Champions are able to take on this role with little to no assistance from IT.
More training needed but still the ability to take some load off of IT.
If you do not have a skilled SharePoint Developer on staff think about the future and the lifecycle of your application. Contractors are great people and many of them do a great job but the more customizations you do the more support you will need.
Collaborate with your colleagues in content management.Design your technical and information architectures for the long haul. No one and rebuild situations.Define an application-development role, and always think ahead.Custom Development - choose your third-party partners.Do you have a lot of third-party code? Test integration into your platform and workloads.Get in front or at least think about the future - Office 365Mandate UAT TestingLISTEN TO YOUR USERS!!
Good vs. EvilAdmins… DevelopersDevelopers Admins…Good vs. Evil Customizing your site without going to… Well, you get the point!
•Consultant with 17 years of IT experience•MCITP•SharePoint & Solution Sales•SharePoint 2007 & 2010 Administration•Lotus DominoNotes Administrator for 12 years•Migrations, Assessments, Discovery, Implementations, etc.•Works with 3rd party partners to deliver end to end solutions to clients.•Blog: http://www.notjustsharepoint.com•Enjoys speaking at user groups and events!!•Co-host on SPTV http://mysp.tv•THE BOOK…yes in my spare time co-authoring a book on ManagedMetadata!! Stacy L. Deere Focal Point Solutions, LLC. Owner
Agenda• Show of hands (Be Honest!)• What I mean by Good vs. Evil in customizations• Something to start making you think…hmmm• Design vs. Branding• Survey Facts by Forrester• Conflicted Anyone?• Whose right or whose wrong (Which way do I go?)• Some short stories…• Making the right customization decision.• Proceed with Caution• Governance….yes I said it!• Best Practices• Q&A• Contact Information
Design vs. BrandingDesign is the visual appearance of a page. Where artistic style, designprinciples are put into place to creatively and effectively display each elementof the page. How the customer responds to the feeling they get when clickingon a Web page is very important. It can determine whether a visitor choosesto continue to explore the site or move on to the next site.Branding is a strategy. The ‘behind the scenes’ work that goes on in the firststages of site development. Branding encompasses detailed competitiveanalysis, business goals, evaluation, marketing collateral design and targetaudience definition. It gives the site direction and objectives and is essentialto the success of the site.
Some Survey Facts Provided by Forrester• Customers are quickly adopting SharePoint 2010. Fifty-seven percent of respondents using SharePoint had already upgraded to SharePoint 2010, a fast pace for a platform product available for only 14 months. Adoption is strong across industries and sizes of enterprise.• Most of our survey respondents start with SharePoint’s most familiar “workloads” before proceeding to more comprehensive use of the platform. Customer-facing websites and custom applications were used the least widely. For about half the respondents, SharePoint took longer than expected to implement for a variety of reasons.• About three-quarters of respondents said that IT and business sponsors are satisfied with SharePoint. This indicates to us that most customers are willing to tolerate some issues for strategic initiatives like a SharePoint implementation. SharePoint’s business value for these respondents outweighs its hassles, and SharePoint’s future looks bright.
Even Super Heros get conflicted…Yes even Spidey!
The Conflict• SharePoint can be a productive platform for business applications. SharePoint can help your teams deliver applications fast in three ways. First, with a little customization of the human interface, SharePoints out-of-the-box applications can work for many situations. Second, SharePoints basket of developer services for applications involving collaboration, social media, website creation, workflows, document management, information distribution, search, and reporting dashboards can speed completion of projects. Third, you can delegate simple sites and workflows, as well as content updating, to businesspeople.• Customization challenges stability, performance, and upgrades of your shared service. The more custom code in your SharePoint farm, the greater the risks to the integrity of that farm. A SharePoint environment is a shared service, providing applications to many departments, teams, and groups. One groups decision to enhance its SharePoint site with custom code can compromise availability and performance of every other groups applications. Also, as customers using MOSS 2007 are discovering, some human-interface customizations are impossible to port to SharePoint 2010.
Management?Developers? Administrators?Consulting Firm? Business Users? A Committee?
The StoryFleeing the wars that devastated their home planet of Cybertron, most of the Autobotsmade Earth their temporary home. Under the leadership of the powerful robot, OptimusPrime, the heroic Autobots battled fearlessly against the assaults of the evilDecepticons, protecting their new human friends.Ok not the story you were looking for? Good vs. Evil Customizing your site without going to….well you know!
Customer wanted to addremove announcements… Template needs to be reusable…hardcoded URL’s? THE EVILUsers who are they? FACTS!!! Packaging? What’s that? Customer wanted to update a link… Story Time Over doing Social Media…Yes these are all true!
Basic Customizations (OOTB)Allows the end user that is familiar with SharePoint to create sites, lists andweb parts through the user interface fairly easily to produce something thatmeets their requirements.Strengths – Quick to create – Basic SharePoint Knowledge – Encourages consistency….the "SharePoint way"Weaknesses – Little to no flexibility (You will make compromises!) – Repeating your customizations in a solution are limited - manual repetition of creation steps or templates.
SharePoint Designer (SPD)Allows power users to get a bit more creative to use more advanced optionsin such as custom workflows and the use of data sources.Strengths – More Options • Easier to fulfill more requirements – Creation and changes to master pages and page layouts (Look and Feel)Weaknesses – Difficult to deploy customizations to other sites – Example: A custom workflow created in SPD is applied to a specific list and cannot be reused on another list. The only option is to manually recreate the workflow again for the next list. – If the power user is untrained a lot of damage can be done very quickly – Once files are customized by SPD they cannot be changed by custom code
Custom DevelopmentRequires a skilled SharePoint developer to write it but it is the most powerfuloption that opens up the full SharePoint API, web services and any other codeyou want to use to customize your solutions.Strengths – Provides the most options – Customizations can be packaged up as features that are easily deployed and reused in multiple solutions – Deployment can be controlled and governed more easily as customizations can only be deployed by people with SharePoint admin permissionsWeaknesses – Requires a skilled SharePoint developer – Takes longer to achieve the same results
Warning Signs• Dev. thinks building a package for deployment means a site template. (Reminder - You can’t change a site template once you choose it)• Hardcoded URL’s• Dev states he can’t create a master page on the server and when instructed to do it from his computer he says I don’t use Microsoft.• Changing a link or announcement requires you to know code.• Developer knows development but does not know SharePoint…• Style changes should not be done in the Master Page. That’s what the css is for (aka style sheet)• Do Not modify the corev4 (This is the OOTB style sheet for SP)• Do Not change any OOTB files make a new one.• Avoid the rabbit hole of non-stop customization requests and tweaks. – There’s always going to be a new version or phase
Governance - Customization• Document approved customization tools. – Example, decide whether to allow the use of Microsoft SharePoint Designer 2010 and specify which site elements can be customized, and by whom.• Manage your source code – use a source control system, and set standards for documenting the code.• Coding Best Practices (Dev. Standards)• Set testing and verification standards (Dev, QA, Production)• Required packaging and installation methods. – Control the use of sandboxing -- enables site owners to host custom solutions in a partially trusted context so they do not affect the rest of your SharePoint implementation.
Governance - Customization• Define what kinds of customizations are going to be supported. • Example, you might want to allow the use of Web parts to integrate Microsoft Silverlight 3 applications together with SharePoint sites. For more information about kinds of customizations and their potential risks, see Governance and customization and for managing customizations, see the white paper SharePoint Products and Technologies customization policy (http://go.microsoft.com/fwlink/p/?linkid=92311).
Governance - Branding• If you are designing an information architecture and a set of sites for use across an enterprise, consider including branding in your governance plan.• A formal set of branding policies helps ensure that sites consistently use enterprise imagery, fonts, themes, and other design elements. – SharePoint Server 2010, you can import a Microsoft PowerPoint 2010 theme directly into a SharePoint site, which automatically applies the theme to all sub-sites.
Practice does not make Perfect…A Perfect Practice makes Perfect!!
Best Practices• Collaborate with your colleagues in content management.• No 1 and rebuild situations!• Define an application-development role, and always think ahead.• Have an Application Lifecycle• Custom Development - choose your third-party partners.• Test integration into your platform and workloads.• Get in front or at least think about the future!• Mandate UAT Testing• LISTEN TO YOUR USERS!!
Q&A Good vs. EvilCustomizing your site without going to….well you know! Superman gets confused at times…does that mean he’s human?
Twitter: @sldeere Blog: http://notjustsharepoint.com Twitter: My_sptvhttp://mysp.tv Email: email@example.comLinkedIn: http://www.linkedin.com/in/stacydeere My Bat Signals Otherwise known as Contact Info.