Presentation on theme: "SharePoint 2013 customizations and recommendations"— Presentation transcript:
1 SharePoint 2013 customizations and recommendations Jaakko Nikko & Vesa Juvonen Tuesday 5th of March, 2013#td2013fi
2 NotesSharePoint 2013 – Räätälöinti ja suositukset Parhaita käytäntöjä - Microsoft Services esittää - Level Mikä on räätälöintiä?- Milloin kannattaa räätälöidä? - Mitä kannattaa ja voi räätälöidä? - Räätälöinnin vaikutukset hankkeisiin ja kokonaiskustannuksiin - SharePoint 2013 uusien mahdollisuuksien huomioiminen kustomoinneissa - Miten teen kustomointeja jotka toimivat sekä Office365 ja On-Prem puolelle - Mikä on SharePoint:n tulevaisuus räätälöintien osalta ja miten otan tämän huomioon jo ny?
3 Who we are? Jaakko Nikko Vesa Juvonen Senior Consultant Principal ConsultantPassion for delivery excellence24/7 Hands-On SharePoint dudesExpertiseServices delivery
4 Experience | the difference Microsoft Services exists to help you: Achieve | the futureRealise | your visionShare | the experienceAt the forefront of what's possible with Microsoft technologyDetermined to realise and support customers’ business visionDelivering impact through integrated relationshipsMicrosoft Services exists to do three things:We help you achieve the future. We have the expertise to do what hasn’t been done before. To deliver solutions that are at the forefront of what is possible. But it’s not about the technology for technology’s sake…It’s about delivering meaningful impact for your business – and helping you to realise your business vision.And finally, sharing our experience is at the centre of what we do. We help you reduce risk and accelerate deployment – but we do this with you, and alongside partners – allowing you take advantage of the right resources for what you need to achieve.As well as strong partner relationships, we connect across the Microsoft organisation – in particular, working with the product development teams to provide the expertise you need.[CLICK]Let me now take a few minutes to step through each of these three areas.
5 Agenda #td2013fi When to do customizations? What is feasible to customize?Can I safely customize anything?Customization impact to overall costs compared to gained valueWhat’s new in 2013 concerning customization optionsWhat’s the roadmap for SharePoint in future concerning customization and development models?#td2013fi
6 “Use SharePoint as an out-of-box application whenever possible” - Jeff Teper, Corporate Vice President of SharePoint at Microsoft “The New SharePoint” – release note for SharePoint 2013 at 17th of JulyWhy?
7 Why do customers want customizations? UI has to be changed based our brand…”We want something cool or advance…”
8 Why customers want to upgrade to latest versions? ”We want something cool or advance…”
9 What’s number one upgrade blocker? Deployment specific customizations…Those cool and advanced widgets…
10 What’s number one reason for support cases with SharePoint? Deployment specific customizations…Those cool and advanced widgets…
11 What’s number one cost factor in projects? Deployment specific customizations…Those cool and advanced widgets…
12 All customizations are evil! Blocks upgrade to newer versions…Cause additional costs…Blocks access to new and shiny things…
13 “Use SharePoint as an out-of-box application whenever possible” - Jeff Teper, Corporate Vice President of SharePoint at Microsoft “The New SharePoint” – release note for SharePoint 2013 at 17th of July
14 We want to provide newest capabilities without delays… Release cycle will be shorter with SharePoint…“We want customers to be able to take latest versions in to use without constant additional costs related on customizations…”
15 We don’t want customizations! ”Except that we need to have few widgets which do….””Except the user expirience has to be different….””Except that we have specific taxonomies which….”We don’t want customizations!”Except that we don’t like the UI for ordering sites….””Except that we would like to see customers from SAP in front page….””Except that we want social to be EXACTLY like in Facebook….””Except that we need few new page layouts….””Except that someone said that we need to do x for SharePoint….”
16 Customers and partners need to be able to customize and modify SharePoint experience… This business is not going away…“We want SharePoint to be customized in way that it’s beneficial for all parties… Amount of work is not going away, it’s just evolving…”
17 We can do this using multiple different ways…. ”I just want things to work – I don’t care how you do it!”You should!Long term costs are in the details and you own the platform…
18 Solve the business requirements and objectives Thinking long term and not just getting things done short term…Do you really need to have full trust solutions to achieve the business objective?Is server side just easier to develop based on earlier knowledge?
20 What do we really want to do in project? -What do we really want to do in project?What’s critical for the project?MustWhat could be benefical and shoud be done?ShouldWhat brings additional value and could be done?CloudProof of concepts or pilotsMinimizing risks and collecting feedback from smaller group advance
21 ”We don’t have time to think what to do – we need to just do it!” That’s interesting way to do business…Really?
22 ”We just upgraded to 2010 and now 2013 is out – upgrade is too expensive.” What are you upgrading?End user platform for social and collaboration or meaningless customizations developed only for you?
23 Agility vs. Risk vs. Costs Choosing the right model for you based on your business needs – not on random blog posts in Internet…
24 ”It takes us 6 weeks to get something updated due to our release model” If this is not what your looking for, change the model – product doesn’t require itChange it!
25 ”Every widget for SharePoint costs tens of thousands…” No it doesn’t!You should looks for second opinions as well…
26 SP Apps – From pieces to “ready to use solutions” -SP Apps – From pieces to “ready to use solutions”Packaged solutionsReady to use appsFunctionality in a boxOut of the shelfReusable as suchFor specific functionality…Web PartsListsContent typesControls…* “Conceptually at least…. We’ve done a great job selling boxes of Lego bricks in the past but the sticking points always came down to – “what do I build with SharePoint?”. People know Legos are great but if you ask them what to build they would shrug their shoulders.* I’m hoping that apps open up new doors for things like the HR app, the Procurement app, etc. and help us compete better against the likes of Saleforce.”
27 Access Apps – business customizations on-demand
30 SharePoint 2013 development controversy Apps, apps, apps, apps, apps, apps, apps, appsOffice365 doesn’t support server side codeSandbox solutions are ”deprecated”“Apps can’t do everything I’ve done in past”
31 Impact of customizations -Impact of customizationsHigh availabilityDirect impact on SLA and availability of the platformMaintenance and operational costsCustomizations will cause additional costs short and long termAgility for business to deploy new widgetsAgility for IT to ensure that they can support businessAlign with the cloudCustomizations can block cloud or make migration much more complex and more expensive
32 Classic SharePoint customizations Full trust solutions with ghosted filesImplications to DR modelDeployments always cause downtimeImpact on SLAs and availabilityFull trust solutions have to be closely analyzedDo you trust your solution fully?Complex ALM processesNot available in Office365Not available in Office365-D even in future
33 What if… We would use same model for on-premises and cloud? Is that Tobias?
34 Cloud Application Model (CAM) Forget full trust solutions completely – run things on client side as much as possibleClient side APIs highly improved in 2013Embrace un-ghosted deployment modelsSimplicity for operations, like DRProvisioning directly to database as needed also in on-premisesRemote provisioningPerform updates using client side codeHardcore code located outside of the SharePointNo full trust codeOffice365-D will also drop support pretty soonNo Sandbox solutionsDeprecatedRemote provisioningCreate necessary elements cross site collections by running code outside of the SharePointUn-ghosted deployment of artefactsApps as one dimension of the approach
35 Denial is the first step… Product roadmap is clear though…
36 Remember when feature framework and solutions where introduced… “F that… too difficult – I’ll keep on modifying oob files…”
37 Or when you were told that you’ll have to learn CAML…
39 Does this mean that full trust solutions should not be created? It means that you should use client side technologies when possible and use classic models as secondary option…
40 Understand needs and challenge what you have… IT Systems can help business, if they are built for supporting business…There should be business case for each IT System…
41 “Vähemmän himmeleitä - enemmän pilveä” - Turkka Keskinen, Tietohallintojohtaja, UPM, CIO100Blogi, tietoviikko.fi/cio at 9th of Nov 2012”Kustannuksia lisääviä tekijöitä ovat monimutkaisuus ja huono tekemisen laatu.””Standardijärjestelmän käytettävyyttä voidaan tarvittaessa ”tuunata” web-teknologioita hyödyntäen.””On hyvä muistaa, että tehokkain prosessi on sellainen, jota ei edes tarvita. Joskus kannattaakin jättää koko juttu tekemättä.”Keskiviikko CASE UPM Sharepoint liiketoimintaprosessien tehostajanaJaakko Kortesmäki, Director, Custom Applications, UPM Kymmene
42 Wrap up… Configure before customize… SP2013 provides more agile customization options…Apps is one dimension of this, but also other client side technology approaches can be taken…Wrap up…Try avoiding full trust code where possible… long term impact on costs…Aligned with the cloud…Configure before customize…Evaluate business case in impact of your customization models short and long term…Minimize impact of customizations on upgrades…