sharepoint 2013 customizations and recommendations jaakko nikko & vesa juvonen tuesday 5 th of...

SharePoint 2013 customizations and recommendationsJaakko Nikko & Vesa JuvonenTuesday 5th of March, 2013#td2013fi

Who we are?

Senior Consultantjaakko.nikko@microsoft.com

Principal Consultantvesa.juvonen@microsoft.com

Jaakko Nikko Vesa Juvonen

Passion for delivery excellence Expertise

24/7 Hands-On SharePoint dudes Services delivery

Experience | the differenceMicrosoft Services exists to help you:

At the forefront of what's possible with Microsoft

technology

Achieve | the future Realise | your vision Share | the experience

Determined to realise and support customers’

business vision

Delivering impact through integrated relationships

RégisLaurentDirector of Operations, Global KnowledgeCompetencies include:Gold LearningSilver System Management

Agenda

#td2013fi

• When to do customizations?• What is feasible to customize?• Can I safely customize anything?• Customization impact to overall

costs compared to gained value• What’s new in 2013 concerning

customization options• What’s the roadmap for

SharePoint in future concerning customization and development models?

“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

Why?

Why do customers want customizations?

UI has to be changed based our brand…

”We want something cool or advance…”

Why customers want to upgrade to latest versions?

”We want something cool or advance…”

What’s number one upgrade blocker?

Deployment specific customizations…Those cool and advanced widgets…

What’s number one reason for support cases with SharePoint?

Deployment specific customizations…Those cool and advanced widgets…

What’s number one cost factor in projects?

Deployment specific customizations…Those cool and advanced widgets…

All customizations are evil!

Blocks upgrade to newer versions…Blocks access to new and shiny things…

Cause additional costs…

“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

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…”

We don’t want customizations!

”Except the user expirience has to be different….”

”Except that we want social to be EXACTLY like in Facebook….”

”Except that we need to have few widgets which do….”

”Except that we would like to see customers from SAP in front page….”

”Except that we don’t like the UI for ordering sites….”

”Except that we need few new page layouts….”

”Except that we have specific taxonomies which….”

”Except that someone said that we need to do x for SharePoint….”

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…”

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…

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?

What do you really want to achieve?

-

Why?

What do we really want to do in project?What’s critical for the project?Must

What could be benefical and shoud be done?Should

What brings additional value and could be done?Cloud

Proof of concepts or pilotsMinimizing risks and collecting feedback from smaller group advance

-

”We don’t have time to think what to do – we need to just do it!”

Really?That’s interesting way to do business…

”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?

Agility vs. Risk vs. Costs

Choosing the right model for you based on your business needs – not on random blog posts in Internet…

”It takes us 6 weeks to get something updated due to our release model”

Change it!

If this is not what your looking for, change the model – product doesn’t require it

”Every widget for SharePoint costs tens of thousands…”No it

doesn’t!You should looks for second opinions as well…

SP Apps – From pieces to “ready to use solutions”

• Web Parts• Lists• Content types• Controls• …

• Packaged solutions• Ready to use apps• Functionality in a box• Out of the shelf• Reusable as such• For specific

functionality• …

-

Access Apps – business customizations on-demand

Access Apps for agility

Simplified design experiencePre-defined schema templates (nouns)Build a functioning app in 60 secondsAutomatic generation of navigation, forms and buttonsSimplified, code-free configuration and customization

Polished, professional resultsApps automatically have an attractive, easy-to-use interfaceConsistent user experience across all apps

SP Apps & Access Apps

demo…

SharePoint 2013 development controversy

Apps, apps, apps, apps, apps, apps, apps, apps Office365 doesn’t support server side

codeSandbox solutions are ”deprecated”“Apps can’t do everything I’ve done in past”

Impact of customizationsHigh availabilityDirect impact on SLA and availability of the platform

Maintenance and operational costsCustomizations will cause additional costs short and long term

Agility for business to deploy new widgetsAgility for IT to ensure that they can support business

Align with the cloudCustomizations can block cloud or make migration much more complex and more expensive

-

Classic SharePoint customizations

Full trust solutions with ghosted filesImplications to DR model

Deployments always cause downtimeImpact on SLAs and availability

Full trust solutions have to be closely analyzedDo you trust your solution fully?Complex ALM processes

Not available in Office365Not available in Office365-D even in future

What if… We would use

same model for on-premises and

cloud?

Cloud Application Model (CAM)

Forget full trust solutions completely – run things on client side as much as possibleClient side APIs highly improved in 2013

Embrace un-ghosted deployment modelsSimplicity for operations, like DR

Provisioning directly to database as needed also in on-premisesRemote provisioningPerform updates using client side codeHardcore code located outside of the SharePoint

Denial is the first step…

Product roadmap is clear though…

Remember when feature framework and solutions where introduced…

Or when you were told that you’ll have to learn CAML…

Redefining application models for SharePoint

Classic - Full trust solutions

• ISV solutions• Platform level

customizations to on-premises

• Custom service applications

• Custom WCF services• SharePoint

customizations, not customer specific customizations

Client Side Solutions

• Server side controls as JavaScript on page layouts and master pages

• Remote provisioning for elements

• Embracing un-ghosted model

• SP App dimension with provider hosted apps to provide new capabilities

• Customer specific customizations

SP Apps

• App catalog based solution

• Packaged reusable solutions built for specific functionality

• Not only for market place or store, but also as platform for customer specific customizations

Does this mean that full trust solutions should not be created?

NO… It means that you should use client side technologies when possible and use classic models as secondary option…

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…

“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ä.”

Wrap up…

SP2013 provides more agile customization options…Apps is one dimension of this, but also

other client side technology approaches can be taken…

Configure before customize…

Evaluate business case in impact of your customization models short and long term…

Try avoiding full trust code where possible… long term impact on costs…

Minimize impact of customizations on upgrades…

Aligned with the cloud…

t

Q&A

Keskustelu jatkuu:https://www.yammer.com/spug

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.